252414 - delays page display when AAAA record not available.

Status: VERIFIED INVALID

(Firefox :: General, defect)

Description

[martin f. krafft]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040614 Firefox/0.8
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040614 Firefox/0.8

The domain takes ages to resolve. I think this is because their DNS server does
not respond properly to AAAA (IPv6) requests and thus the requests have to
timeout before Firefox displays the page as retrieved via IPv4. For e.g.
www.yahoo.com, the AAAA request immediately returns a negative response and thus
firefox can display the page with IPv4 almost immediately.

The problem is that many domains don't handle AAAA properly and thus quite a few
pages take ages to load in firefox, which first queries IPv4 then IPv6 and only
then displays the page.

Couldn't it be made to use IPv4 if available for now? IPv6 isn't really
production yet. Or maybe the timeout can be decreased from 25 seconds to
something like 4 or less.

Reproducible: Always
Steps to Reproduce:
1. Fire up a packet sniffer for port 53 tcp/udp
2. Visit www.allmusic.com in firefox
Actual Results:  
25 seconds load time.

Expected Results:  
load immediately when the IPv4 A request returns.

Comment 1

[Jo Hermans]

allmusic.com has a misconfigured DNS-server. See bug 68796. Do you still have
the same bug in Firefox 0.9 ?

doubleclick.net was added as an exception (preference
network.dns.ipv4OnlyDomains), but allmusic.com wasn't in that list. But you
should be able to disbale IPv6 all together, with preference
network.dns.disableIPv6. Both prefernces can be set in about:config.

Comment 2

[martin f. krafft]

i have also been experiencing problems with doubleclick, but then maybe that's
because i am using 0.8 still and it has been fixed since.

i guess, since 0.8 does not have network.dns.* in about:config.

thanks for the pointer still. i am glad this is already fixed. i told
allmusic.com in the meantime to fix their dns servers.

thus i guess i can mark this closed.

Comment 3

[martin f. krafft]

I note that allmusic.com has amended their DNS records following my request and
now properly answer (negatively) to AAAA requests. They therefore do not have to
be excluded from IPv6 lookups like doubleclick.

Has anyone contacted doubleclick.net?

Comment 4

[Jo Hermans]

was fixed  along time ago in bug 377395