[Bug 456224] Re: Installing bind9 with forwarders causes loss of hostname resolution.
netsupport at copyrightwitness.net
Thu Oct 22 09:24:46 BST 2009
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
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.
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
More information about the Ubuntu-server-bugs