[Bug 456224] Re: resolver doesn't fall back to localhost server if resolv.conf is empty

[Thomas Hood]

It is the case in Quantal, anyway.

** Changed in: eglibc (Ubuntu)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to eglibc in Ubuntu.
https://bugs.launchpad.net/bugs/456224

Title:
  resolver doesn't fall back to localhost server if resolv.conf is empty

Status in “eglibc” package in Ubuntu:
  Fix Released

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/named.conf.options contains:
  -------------
  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;
          };

          auth-nxdomain no;    # conform to RFC1035
          listen-on-v6 { any; };
  };
  -------------
  Taking the DNS servers into /etc/resolv.conf and uninstalling bind9 results in hostname resolution being restored.

  
  THIS WORKS UNDER Ubuntu Intrepid 8.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/456224/+subscriptions