4 ms·
Although the article does cover this, perhaps it doesn't emphasize the point strongly enough: The IP addresses for your authoritative servers are going to be s
by dboreham 9y ago
Although the article does cover this, perhaps it doesn't emphasize the point strongly enough:
The IP addresses for your authoritative servers are going to be stored in the glue record for your zone, which is physically held in the root servers (i.e. not your servers).
Those glue records can't be changed quickly.
Therefore you need to be very sure that your servers' IP addresses are really static.
We run our own DNS (for mostly historical and paranoia about reliability reasons). One of our servers is on a subnet that we own, so that totally under our control. The other is at a provider where I have had a detailed back-and-forth with the support staff about the circumstances under which its IP might change, and how to ensure it won't change, specifically mentioning that we are going to run an authoritative DNS server on their infrastructure (currently IBM/Softlayer, moving to Packet.net soon). I am skeptical that a low-cost provider (DO, etc) can give a strong enough guarantee that the machine's IP address won't change.
Makes Route53 look very attractive for common/garden purposes.
- takeda 9y agoDNS doesn't require you to use a glue records though you can just provide name and the resolver will another query to figure the IP. It's of course less efficient and probably you shouldn't do it, but DNS itself doesn't stop you from that. As for authoritative servers what I did in the past is essentially working together with friends, I was backup name server for their domains and they were backup for mine. There are also some free public DNS servers as well.
- dboreham 9y agoTrue. I didn't mention that because as you say you shouldn't do it. A big problem with free/cheap DNS services is that (as far as I have seen) they do not support either secondaries off their network, nor being a secondary to some other primary. So you end up in an all-or-nothing situation where you either rely entirely on one provider, or you have to host yourself.