Stumbled onto 2 VIPs not actively used: - mozillademosorg-engagement.zlb.phx.mozilla.net - mozorg-engagement.zlb.phx.mozilla.net
The mozilliademosorg-enagement entries didn't seem linked to anything. I deleted the traffic group from the load balancer as well as the following DNS entries: mozillademosorg-engagement.zlb.phx.mozilla.net A 18.104.22.168 22.214.171.124 PTR mozillademosorg-engagement.zlb.phx.mozilla.net mozorg-engagement.zlb.phx.mozilla.net is more complicated. The main DNS records for this are: mozorg-engagement.zlb.phx.mozilla.net A 126.96.36.199 mozorg-engagement.zlb.phx.mozilla.net AAAA 2620:101:8008:5::2:b 188.8.131.52 PTR mozorg-engagement.zlb.phx.mozilla.net 2620:101:8008:5::2:b PTR mozorg-engagement.zlb.phx.mozilla.net Based on the contents of affiliates.mozilla.org.conf, it looks like the service names listed below should be handled by whatever is handling affiliates.mozilla.org. This turns out to be the generic cluster (generic.zlb.phx.mozilla.net). Their entries in Inventory were updated. - fb-affiliates.mozilla.org - affiliates-cdn.mozilla.org demos.mozilla.org currently points to mozorg-engagement.zlb.phx.mozilla.net; I can't find it as a ServerAlias or ServerName in any of the HTTP config files within puppet. I deleted it: demos.mozilla.org CNAME mozorg-engagement.zlb.phx.mozilla.net I also deleted the following related records. There were no ping responses to either IP address. demos-dev.allizom.org A 184.108.40.206 demos.allizom.org A 220.127.116.11 engagement-dev.zlb.phx.mozilla.net A 18.104.22.168 engagement-stage.zlb.phx1.mozilla.net A 22.214.171.124 126.96.36.199 PTR engagement-dev.zlb.phx.mozilla.net 188.8.131.52 PTR engagement-stage.zlb.phx1.mozilla.net
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.