jp mentioned in IRC that AWS Route53 is really useful for DNS, because it has failover capability, low TTLs, and is AWS’ most stable service. This made me wonder if it’d be useful for us to have for mozilla-community.org and/or communitysysadmins.org. Obviously we’d have to have the nameservers pointed to AWS, so for mozilla-community.org, MoCo/MoFo (whoever controls it) would have to hand control of DNS to us, which is something they may not want to do. Is this something we’d want to use? If so, how do we make a case to get control of the DNS?
2 Likes
I’d recommend testing with communitysysadmins.org. I control that domain and can delegate it to Route53.
That sounds good to me, tanner, want to give it a go? Not sure you guys can decide if you want it until you’ve tried it
Sounds good. @mrz, if you can get me a list of DNS records for the domain
and all its subdomains, I can get it added to AWS later.
; SOA Record
COMMUNITYSYSADMINS.ORG. 3600 IN SOA ns57.domaincontrol.com. dns.jomax.net (
2014021400
28800
7200
604800
600
)
; A Records
@ 1800 IN A 54.243.190.28
@ 1800 IN A 54.243.190.39
@ 1800 IN A 54.243.190.47
@ 1800 IN A 54.243.190.54
boris 3600 IN A 15.185.186.109
discourse 3600 IN A 15.185.182.101
natasha 3600 IN A 15.126.202.107
phab 3600 IN A 15.185.222.145
phab-web1 3600 IN A 15.185.164.166
phab-web2 3600 IN A 15.185.158.81
chef-server 3600 IN A 15.126.201.238
csa-monitor1 3600 IN A 15.125.81.130
csa-bastion1 3600 IN A 15.125.119.43
; CNAME Records
signup 3600 IN CNAME host.launchrock.com
www 3600 IN CNAME phab.communitysysadmins.org
; MX Records
@ 3600 IN MX 5 mail.velvet.org
; NS Records
@ 3600 IN NS ns57.domaincontrol.com
@ 3600 IN NS ns58.domaincontrol.com
Awesome, thanks. I’ll work on this when I get home, and get the name servers to you.
Done. Nameservers:
ns-1025.awsdns-00.org.
ns-2035.awsdns-62.co.uk.
ns-155.awsdns-19.com.
ns-863.awsdns-43.net.
Screenshot, if all looks okay you can switch over any time.
This is done.
Since you guys are managing discourse, I’d be interested in moving mozilla-community.org over to route53 too. Discourse is the only app running on it right now, but I’d quite like to add CNAMEs for Google Apps, Plesk etc, but I feel bad bugging IT about changing our DNS for us constantly.
When you decide if you like route53, let me know, and I can either move mozilla-community.org over to route53, or, should you decide against it, I can point it at another DNS service (Will mentioned building our own, actually)
I don’t want to build our own DNS server. That’s fine internally, I’d
rather not externally.
I’m fine with moving the DNS to Route53, if nobody else has objections I
say to go ahead. Just give be a BIND file or list of records and I’ll
import them.
mozilla-community.org is now hosted on Route53. DNS change requests should go in Phabricator, not Bugzilla.