our record sets are currently on mozilla-labs Need to move to mofo.
Created attachment 8454882 [details] mozilla-community.org BIND file I've moved the zone files for mozilla-community.org over. Also, I've attached it for reference For now, discourse.mozilla-community.org has been assigned as a CNAME to csa-discourse-lb1-1054466604.us-west-1.elb.amazonaws.com When discourse is moved to this account, we can convert this to an alias. @tanner, can you give a +1 to move the nameservers?
Comment on attachment 8454882 [details] mozilla-community.org BIND file As discussed on IRC, we need to clean this up a bit. r- for now, I'll clean it up and attach a new one.
Created attachment 8455026 [details] dns.txt I removed some of the unused stuff, and updated others. I *think* I did the WPMS alias right.
Comment on attachment 8455026 [details] dns.txt ooh. Mostly good, but I've just noticed that the ALIAS is using a dualstack address. We need to use the standard address (just remove dualstack.)
Attachment #8455026 - Flags: review-
Attachment #8455026 - Flags: review?(tom) → review-
Created attachment 8455030 [details] dns.txt
Attachment #8455030 - Flags: review?(tom) → review+
:tanner Any objection to moving DNS over? Can confirm that the new Route53 config returns working IP addresses for: Discourse WPMS l10n They're the only sites in production, right? One thing which does concern me is ➜ .ssh nslookup discourse.mozilla-community.org ns-286.awsdns-35.com Server: ns-286.awsdns-35.com Address: 18.104.22.168#53 Name: discourse.mozilla-community.org Address: 22.214.171.124 Name: discourse.mozilla-community.org Address: 126.96.36.199 Why two IPs?
mozilla-community.org is already at Route 53. Resolving.
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.