Closed Bug 224463 Opened 21 years ago Closed 21 years ago

DNS: resolving host takes much longer that it should

Categories

(Core :: Networking, defect)

Product:
Core
Component:
Networking
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED WORKSFORME

People

(Reporter: mozilla06b, Assigned: darin.moz)

References

(
URL
)

Details

(Keywords: perf) 

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

When opening mozilla for the first time, resolving the first host takes a long
time. A ping or nslookup of the same host returns immediately.

Reproducible: Always

Steps to Reproduce:
1. Open mozilla browser
2.
3.

Actual Results:  
Status message appears "resolving host ...." and mozilla sits there. After a
while, probably a timeout period, the host is resolved and the web page opens.

While mozilla is still resolving, a ping of the host returns immediately with
ping times.

Expected Results:  
Mozilla should have resolved the host. If ping can resolve the host almost
immediately, mozilla should be able to.

Using Multizilla and Skypilot theme.
Disabled Multizilla and changed to Classic theme and problem still exists.
URL: http://www.foxnews.com → http://www.foxnews.com/
Keywords: perf
Summary: Resolvng host takes much longer that it should → DNS resolving host takes much longer that it should
Was this fixed by bug 223811 (in the latest trunk build) ? I'm not seeing an
AAAA-record for www.foxnews.com though ...
> www.foxnews.com
Server:  gei.grifent.com
Address:  192.168.1.2

Non-authoritative answer:
Name:    a20.g.akamai.net
Addresses:  209.51.177.25, 209.51.177.33
Aliases:  www.foxnews.com, www.foxnews.com.edgesuite.net

>

Could the problem be that the site resolves to more than one IP?

I have tried a couple of sites for startup sites that resolve to only one IP and
they resolve and open quickly. I have not searched for sites that resolve to
multiple IPs to test the oposite case.
WORKSFORME.  what version of linux are you using?  and what version of glibc do
you have installed?  (you can type: "ls -l /lib/libc.so*" to find out.)
/lib/libc.so.6 -> libc-2.2.4.so

Seems to work ok with this build 
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031103 MultiZilla/1.5.0.3l
John: can we mark this "works for me"?
Summary: DNS resolving host takes much longer that it should → DNS: resolving host takes much longer that it should
Yes
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
V per reporter.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.