Resolv.conf did have two lines with nameserver entries for the two entries that were moved to Bind9.
This configuration WORKS under Hardy Heron and AFAIK intrepid. The problem is resolved via an entry in resolv.conf of 'nameserver 127.0.0.1'. 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? This is a CHANGE from operation under Hardy Heron - The reason for me raising the issue is to ascertain that this is now correct behaviour - given that ping and dig both work with an identical setup under hardy heron. Is it that the libc name resolution stack has changed? -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
