5 ms·
"To host your own DNS servers the registrars require you to list two IP addresses with the idea that you'll be providing redundant service. The one thing you do
by jstanley 14y ago
"To host your own DNS servers the registrars require you to list two IP addresses with the idea that you'll be providing redundant service. The one thing you don't want is downtime with DNS, it screws everything up."
I've got around this by having two hostnames for one machine.
The way I see it, since all my services are on this one machine anyway, I'll have bigger problems than DNS if the machine is down: there will be nothing at the address the names are pointing to, so who cares if they resolve properly?
- zrail 14y agoFair point. I've got email and DNS distributed onto both machines so I don't lose anything, and prgmr was pretty clear that I couldn't have a second IP just to fake out DNS so I went with a whole second server.
- uxp 14y agoAlso, if your email box goes down and is unreachable then the sending server should retry later when it can't get a response. If that box is also your DNS server, and the sending email server is unable to lookup the MX record it will automatically bounce. Having a slave/secondary email server should mitigate this to some extent though. Many applications do plan for unreachable services, but throwing the fault down the stack screws up how the error is handled. You can still use a primary application server box as a DNS server, but I would be certain that it's a secondary/slave server, not the primary server.
- eCa 14y agoThat sounds weird (what prgmr said). I've had dedicated servers running dns at several providers for ten years, and all I've ever done is get a second ip for the same machine and bind it to a different hostname.
- agwa 14y agoThings are different now. IPv4 addresses are almost gone so ARIN requires ISPs to have valid justification for every IP address they hold. "Faking out DNS" is not a valid justification.
- lsc 14y agoI wasn't trying to sell you another server. conventional wisdom is that you should have your secondary DNS on a different server, on a different network, run by a different provider, not another server with me.
- zrail 14y agoOh I know, that's why I've got what I have :)
- andreasvc 14y agoI think it's fairer to say you got around to it because they're not checking. Even with a single machine it's still better to have redundant DNS. You want to be able to move around the machine to a new connection / IP, without having to wait for the registrars to update the IP of the DNS server; similarly when your one DNS provider is DDOSed, your site will stop working, but not if you had 2 different providers. So to answer your question: you as the operator will care, because you want to get things back up quickly ... I think for small servers it's much preferable to run a hidden primary (not publicly listed in DNS), and let secondary DNS servers update from there. That way you have complete control over your DNS, even when your machine goes down.