DNS

[Nobody's Hero]

We are running DNS on a windoze server. I am trying to use ITO/NNM to gather some info. I have a feeling that DNS lookups are taking a long time.

1) what is a reasonable lookup time, (I guess In Milleseconds)

2) What command can I use to see how long an nslookup took? I tried `time` but I know there is another way, maybe with an ITO command.

[harry d brown jr]

what version of BIND are you running on your HPUX boxes? If you are using BIND 9.2 or higher you can/should use "dig" instead of nslookup.

and yes, milli sec is good!

live free or die
harry

[Jim Mallett]

Robert,

You should definitely be expecting subsecond response for DNS, anything else and there is likely an issue. (Not necessarily related to DNS though).

Are you timing this from a Unix box?

You could do: timex nslookup host

Everything comes back for me at .01

Jim

[Geoff Wild]

In case you don't have bind on your HP server, and just want dig:

http://eigen.ee.ualberta.ca/hppd/hpux/Networking/Admin/dig-2.0/

timex is the way to see how long a command takes...

Rgds...Geoff

[Uday_S_Ankolekar]

If you are DNS resolve taking place longer time then expected on Unix box then probably you will have to check these two files /etc
1. nsswitch.conf
2. resolve.conf

In resolve.conf check if the domain name , and and dns server fqdn is given in correct order.

nsswitch.conf should have entries for DNS followed by files for the hosts entry for resolving adress.

-USA..

[harry d brown jr]

Robert,

take a look at this:

http://www.mit.edu/afs/net/project/bind/9.2.0/contrib/queryperf/

it allows you to do query testing.

live free or die
harry

[Muthukumar_5 · Accepted solution]

1) DNS lookup time is designed based on the settings on /etc/nsswitch.conf to the corresposding entries as hosts or passwd or etc.

If you take hosts: entry means,
it will resolve in the order specified over there.
Example:

hosts: dns files ldap

hostname's are resolved as
dns --> /etc/resolv.conf
files --> /etc/hosts
ldap --> ldap data base

If you use some return types as like,
[NOTFOUND=return] then it will return when there is not entry out there.

And more if you are doing resolvation using DNS your /etc/resolv.conf settings for nameserver must be in order so that it can handle without taking time.


2) You can use nslookup and as well as nsquery to know the resolvation of entries there. You can use timex / time / times commdns to determine this.

timex command is good to do.

[Carlo Corthouts]

Hi,

dig is a good tool to figure out the time the dns needs to answer.

If dig is not available to you, maybe you can use the timex command as "timex nslookup ......"

Regards,

[Rgomes]

Hi,

There is Windows version 'dig' available. Check the following link:

http://pigtail.net/LRP/dig/

regards,
Richard