← Back to team overview

desktop-packages team mailing list archive

[Bug 417757] Re: [regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups

 

I'm not sure if this is the same bug I'm experiencing, but if I try to
access a domain without IPv6 address, I get this on tshark:

  0.000000 192.168.2.103 -> 192.168.2.254 DNS 74 Standard query AAAA one.ubuntu.com
  0.074500 192.168.2.254 -> 192.168.2.103 DNS 135 Standard query response
  0.074682 192.168.2.103 -> 192.168.2.254 DNS 95 Standard query AAAA one.ubuntu.com.internal.eudemo.info
  0.075854 192.168.2.254 -> 192.168.2.103 DNS 95 Standard query response, No such name
  0.075991 192.168.2.103 -> 192.168.2.254 DNS 74 Standard query A one.ubuntu.com
  0.147486 192.168.2.254 -> 192.168.2.103 DNS 106 Standard query response A 91.189.89.219 A 91.189.89.218

As you can see, between the AAAA and the A resolution there's a wrong query with my local domain added: this is the one which takes a few seconds to fail (not in this case because I have setup my dnsmasq with local=/internal.eudemo.info/ to get a fast response)
I have tested it with both Firefox and Chrome and both do the same, so I assume is a system problem. Is this the same problem or I need to open a separate bug report (or something is wrong with my setup)?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/417757

Title:
  [regression] all network apps / browsers suffer from multi-second
  delays by default due to IPv6 DNS lookups

Status in “eglibc” package in Ubuntu:
  Triaged
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “eglibc” source package in Lucid:
  Triaged
Status in “network-manager” source package in Lucid:
  Invalid
Status in “eglibc” source package in Karmic:
  Fix Released
Status in “network-manager” source package in Karmic:
  Invalid
Status in “glibc” package in Fedora:
  Confirmed

Bug description:
  In Karmic, DNS lookups take a very long time with some routers,
  because glibc's DNS resolver tries to do IPv6 (AAAA) lookups even if
  there are no (non-loopback) IPv6 interfaces configured. Routers which
  do not repond to this cause the lookup to take 20 seconds (until the
  IPv6 query times out).

  *** PLEASE DO NOT COMMENT ON THIS BUG unless you have something
  constructive to say. Everything that can be said has already been
  said, and if you comment, you are just adding noise. Please let those
  that actually know what they are doing concentrate on fixing this bug
  from now on. ***

  If disabling IPv6 or using good DNS servers like openDNS fixes the
  problem, you are not dealing with this bug. Please refrain from
  complaining here in that case

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