I'm still not sure why you recommend not trusting "complex (remote) GUI tools".
simpler is always better. Simpler and LOCAL to my machine is best.
"Complex (remote) GUI tools" (what most people just call "web tools") have one significant advantage over "simple" (local) tools -- they avoid local configuration problems.
nslookup also needs configuration? dig need configuration?
I would estimate that the #1 problem with using nslookup/dig/etc is that the person using the tool runs it on a computer set up to use a local DNS server
nslookup and dig can send a query directly to whatever DNS you tell them to query. I've never heard of configuration problems with nslookup and dig, except in your FUD.
However, for the more knowledgeable, nslookup/dig can provide slightly faster results.
dns is query/response. no need to complicate what is simple
Interesting. I've never come across this problem with nslookup.
it is a very stable, repeatable old problem.
I've used nslookup quite often, and never seen it give erroneous results.
I described how to create the problem. have nslookup query an NS with no PTR record for the IP of NS.
ut you've still managed to avoid explaining why those "complex (remote) GUI tools" (www.dnsstuff.com) should not be trusted.
see above. I try to avoid self-evident, baby-talk explanations unless requested.
Len
_____________________________________________________________________ http://IMGate.MEIway.com : free anti-spam gateway, runs on 1000's of sites
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
