I have been testing nscd for a while and have discovered, alas, that although nscd notices when resolv.conf changes — e.g., when it needs to do a DNS query it uses the correct nameserver address — it does *not* invalidate its hosts cache when resolv.conf changes. This causes problems when connecting to VPNs whose nameservers give different results from those given by external nameservers. I filed a bug report against nscd in the Debian BTS: bugs.debian.org/700385. The executive summary is:
* Nscd doesn't invalidate its hosts cache on resolv.conf changes; * if nscd is supposed to do so then, then please fix the bug; * otherwise please include a resolvconf update script in nscd which invalidates nscd's hosts cache. I wonder if resolvconf should do the nscd hosts cache invalidation itself, using "nscd --invalidate hosts". But considering * nscd is only in universe; * nscd's hosts cache is disabled by default; and * nscd — either the binary or the package — should be responsible for handling resolv.conf changes, not resolvconf, I am reluctant to do so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1110331 Title: nscd no longer needs to be restarted by libc's resolvconf update script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1110331/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
