Mathias Gug wrote: > On Thu, Oct 22, 2009 at 08:24:46AM -0000, cwsupport wrote: > >> Resolv.conf did have two lines with nameserver entries for the two >> entries that were moved to Bind9. >> >> > > I can't reproduce this. Using a standard karmic system, installing the > bind9 package does *not* delete any lines in /etc/resolv.conf. It > doesn't even use the entries in /etc/resolv.conf to setup forwarders (ie > the default bind9 configuration isn't a local cache). > I never said the installer did this. I moved the lines from resolv.conf to the forwarders section. > > >> Before this is discounted though how come DIG still resolves (i.e. >> automatically uses 127.0.0.1) yet PING (and other programs) don't? >> > > DIG bypasses the libc stack (and thus resolv.conf - the same way has > host does) while ping uses the libc stack (and thus uses the information > from resolv.conf). > > > Is the resolvconf package installed on the system? > Yes. Is this expected behaviour from dig? If so then I suspect the libc stack has been fixed and no longer auto-resolves using 127.0.0.1 for DNS services. In which case this can be closed as works for me.
-- Sincerely Yours Copyright Witness Net Support [email protected] www.copyrightwitness.com Registration centre for copyright works. This e-mail and any attachments are confidential and intended for the addressee only. The information in this mail does not amount to legal advice or opinion. Any views or legal references are those of the author and are based on personal opinion or understanding only. -- Installing bind9 with forwarders causes loss of hostname resolution. https://bugs.launchpad.net/bugs/456224 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
