Public bug reported:
If you have an IPv6 nameserver listed in /etc/resolv.conf and it does
not respond to lookups, or is inaccessible for another reason, the
resolver will not check subsequent IPv4 entries.
You can test this by adding an unresponsive IPv6 nameserver to your
/etc/resolv.conf. In this example I've picked on 2001::1.
nameserver 2001::1
nameserver 8.8.8.8
And do;
getent hosts www.google.com
You will get no response. The behaviour will change slightly dependent
on whether your machine has a route for IPv6 traffic or not. If not, it
will return immediately, if it does, it will return after the normal
timeout for a DNS server.
Removing the unavailable IPv6 server works around the problem and allows
the machine to talk to the IPv4 nameservers as normal.
I've tested this on saucy and tahr, identical behaviour on both.
2.18-0ubuntu7 and 2.19-0ubuntu2 on tahr and 2.17-93ubuntu4 on saucy.
== BONUS FEATURE ==
If you encode the IPv4 address in IPv6 notation, everything works!
Use the following in /etc/resolv.conf:
nameserver 2001::1
nameserver 0:0:0:0:0:ffff:808:808
which is logically identical to the entry above, and everything works as
expected.
** Affects: eglibc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1288644
Title:
invalid ipv6 nameserver in resolv.conf breaks resolver
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1288644/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
