|
|
 |  |
Re: Slow Server repliesFrom: Men & Mice Support Date: Wednesday, July 21, 2004
Time: 11:37:32 amWell, keep in mind, there are up to four different things being
looked up, because most versions of nslookup make a bunch of silly
assumptions.
The first thing to be looked up is the server's address. Next, it may
look up the server's PTR record. Then it gets around to looking up
the requested record, possibly followed by a PTR record query for
that.
If I use dig, from the US, the total query time to query your server
and get the response back is less than a quarter second. (This
involves just one query, because lookupd already knows the address of
mail.goya.com.au at this point.)
However, the first several attempts at using nslookup resulted in a
"no such server" error message. So ti took quite a while for my local
name server (running on my PowerBook, as it happens) to look up the
address of your server in the first place. At this point, I can't
tell why this happened.
____________________________________________________________________
Chris Buxton Men & Mice
Customer Support Specialist Making DNS Easy
At 3:59 PM +1000 7/21/04, Nicholas Orr wrote:
>How do you diagnose a slow dns server?
>
>I've got the latest quickdns running on 10.2.8 behind a NAT router
>with every port re-directed to this one machine. If I do a request
>from outside my network such as :
>
>nslookup://webmail.goya.com.au;querytype=A;server=mail.goya.com.au
>
>It takes about 3 seconds to reply. How do I go about debugging this?
>
>Thanks,
>Nick
|

Return to Digital Point Solutions' Home Page |