Fwd: RE: High availability/contingency for DNS?

• Original Message -------- Subject: RE: High availability/contingency for DNS? Date: Tue, 15 Nov 2011 15:16:39 -0600 From: Zito, Matthew <Matt_Zito_at_bmc.com> To: development_at_the-playground.de <development_at_the-playground.de>

Maybe you can forward this to the list for me, as my list setup is borked at the moment.

In any case, DNS is built to be redundant fundamentally. First off, the local resolver on a machine can be configured to look at multiple servers - if one is down, it fails over to the next one automatically. Then, the authoritative servers for zones can be configured with multiple sets - if one returns with an error, servers and resolvers will roll on to the next authoritative machine.

The only place you run into real errors is when a machine believes it is authoritative for a zone but has incorrect data. This can get quite messy, as caching servers will start to hang on to the negative responses, making it difficult to troubleshoot and fix. This isn't the protocol's fault, though, it's really the implementation behaving badly.

Matt

--

http://www.freelists.org/webpage/oracle-l Received on Tue Nov 15 2011 - 15:22:31 CST