Re: DNS is slow
- From: Thorsten Kampe <thorsten@xxxxxxxxxxxxxxxx>
- Date: Fri, 14 Dec 2007 21:46:25 -0000
* (Thu, 13 Dec 2007 11:09:23 -0800 (PST))
My issue is as follows: My machine is very slow to resolve
destination name to ip.
I am running on Windows XP SP2 with the latest security patches.
Using ethereal
Wireshark. If you still have Ethereal, then update.
I can measure that it takes ~5 seconds to resolve a name such as
www.google.com. When I browse to a website referencing many external
sites the web page takes a long time to load (~minutes).
If I run the comand: "nslookup www.google.com" it returns immediately.
This is the wrong query because it will first query for
www.google.com.local.domain . The correct syntax is "nslookup
www.google.com.".
Does anyone have any ideas about how to analyze this issue?
Start by analyzing your thoughts. First you say that name resolution
is slow. Then you say it is fast. So what's true? Did you flush the
DNS cache on the client before the second query?
Do you want to say that "name resolution via Internet Explorer is
slow" versus "nslookup name resolution is fast"? Internet Explorer
does not do any name resolution on its own so your scenario is highly
unlikely.
Anyway: Wireshark is the way to go. But you should use it on the DNS,
not on the client. The DNS forwards your query anyway (as long as it's
not taken from the cache).
Thorsten
.
- Follow-Ups:
- Re: DNS is slow
- From: kevinmr
- Re: DNS is slow
- References:
- DNS is slow
- From: kevinmr
- DNS is slow
- Prev by Date: Re: Cannot access company website from LAN but can from the whole plan
- Next by Date: Re: DNS and internet sites
- Previous by thread: DNS is slow
- Next by thread: Re: DNS is slow
- Index(es):
Relevant Pages
|
