Dan Williams (dcbw@xxxxxxxxxx) said: > It uses bind in a caching-nameserver functionality and named should > _not_ be turned on my default in this configuration. Use of bind as a > caching nameserver was done to work around deficiencies of nscd and > glibc and should allow user applications to be aware of changes > to /etc/resolv.conf faster, since the applications actually just talk to > 127.0.0.1 for the nameserver, and its the caching-nameserver that > actually does the heavy lifting when /etc/resolv.conf changes since > glibc isn't up to the task. Why can't this be solved with nscd and use of 'nscd -i hosts' when resolv.conf changes, out of curiousity? Bill