Thanks. What seems to be happening now is that your system does a
perfectly ordinary IPv4 A record query for bugs.launchpad.net to
192.168.2.1 (the first nameserver in /etc/resolv.conf, which I'm
guessing is your router), gets no reply for five seconds, and then
retries successfully to 68.87.74.162.
In other words, there is still a problem, but it no longer appears to be
anything to do with IPv6. More to the point, I don't think it's anything
that glibc can do anything about either; it's just doing what it's told
to do. At this point I feel comfortable in saying that you should fix
this by way of a configuration change. For example, if 192.168.2.1 is
simply a broken DNS server and you don't really want to use it, but your
router always sends its address out via DHCP, you could edit
/etc/dhcp3/dhclient.conf and use the directives described in the "OPTION
MODIFIERS" section of the dhclient.conf(5) manual page to override it:
for example 'supersede domain-name-servers 68.87.74.162 68.87.68.162
68.87.73.242;' if those addresses are stable.
** Changed in: glibc (Ubuntu Jaunty)
Status: Triaged => Fix Released
--
IPV6 causes slow internet access
https://bugs.launchpad.net/bugs/313218
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
