Re: Unusable DNS, 10.4 Tiger
Re: Unusable DNS, 10.4 Tiger
- Subject: Re: Unusable DNS, 10.4 Tiger
- From: Ryan McGann <email@hidden>
- Date: Thu, 1 Dec 2005 20:29:28 -0800
(2) Can you isolate the problem to the local DNR (Domain Name
Resolver)
versus querying the corresponding name server directly?
IPNetMonitorX
has both a "Lookup" tool that uses the local DNR and a "NS Query"
tool
that allows you to query the corresponding name server directly.
How do
the results compare?
They both are taking about 6-15 seconds today. I may have used NS
Query incorrectly, I entered Qwest's DNS of 205.171.3.65 and tried
nslookup and got:
...
We had the same problem on our corporate network here at work. On one
of our subnets, DNS lookups were taking an obscene amount of time. It
made browsing the Web on a gigabit connection feel like a 33.6K modem.
I tracked it down to two seperate problems:
1) lookupd was crashing nearly *every* DNS lookup. I had hundreds of
crash reports for lookupd. I never fixed that one obviously.
2) Our corporate firewall ruleset was blocking TCP DNS requests. For
some reason the internal DNS server liked to use TCP more times than
it should.
Fixing #2 helped a lot, but it still does NOT feel very "snappy". I'd
be happy to send anybody at Apple the crash reports for lookupd. I
stopped submitting the bug report a while ago; it's stayed in
"anlayze" ever since Tiger shipped.
Ryan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden