resolver doesn't fall back to localhost server if resolv.conf is empty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eglibc (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Up to Jaunty included an empty resolv.conf would make the resolver library fall back to try to use localhost as the nameserver. This is no longer the case in Karmic.
=======
Binary package hint: bind9
Ubuntu Karmic Koala 9.10 BETA
FULLY updated via apt-get dist-upgrade
bind9: 1:9.6.1.dfsg.P1-3
After bind9 is installed hostname resolution no longer occurs on programs such as ping. However dig resolves successfully via the local server.
Bind9 has been configured to execute as a local-cache (i.e. no zones just caching forwarded requests).
/etc/resolv.conf is EMPTY.
/etc/nsswitch.conf contains:
---------------
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
---------------
/etc/bind9/
-------------
options {
directory "/var/cache/bind";
// If there is a firewall between you and nameservers you want
// to talk to, you might need to uncomment the query-source
// directive below. Previous versions of BIND always asked
// questions using port 53, but BIND 8.1 and later use an unprivileged
// port by default.
// query-source address * port 53;
// If your ISP provided one or more IP addresses for stable
// nameservers, you probably want to use them as forwarders.
// Uncomment the following block, and insert the addresses replacing
// the all-0's placeholder.
forwarders {
212.139.132.43;
212.139.132.44;
};
};
-------------
Taking the DNS servers into /etc/resolv.conf and uninstalling bind9 results in hostname resolution being restored.
THIS WORKS UNDER Ubuntu Intrepid 8.04.
Changed in bind9 (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Incomplete |
Oops. I mean Hardy Heron 8.04.