default local DNS failover solution needed, nscd?

Siddhesh Poyarekar siddhesh at redhat.com
Mon Apr 28 01:23:30 UTC 2014


On Fri, Apr 25, 2014 at 06:51:26PM -0400, Chuck Anderson wrote:
> I'm starting a new thread to clarify and emphasize the problem I'm
> actually trying to solve.  Here is the problem restated as I posted it
> to the dns-operations list:
> 
> -----
> Is it really expected that the first DNS server listed in
> /etc/resolv.conf should never go down?  Operationally speaking, who
> can actually rely on listing multiple nameservers in /etc/resolv.conf
> and using libc's failover mechanism in any kind of production server?
> Because the failover behavior in libc is atrocious--each new or
> existing process has to re-do the failover after timing out, and even
> long-running processes have to call res_init() to re-read resolv.conf.

That is because glibc does not maintain a system-wide record of this
and for good reason.  nscd does, but is not feature-complete (no
round-robin for example).

Siddhesh
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20140428/58a977bd/attachment.sig>


More information about the devel mailing list