While it is indeed good to use and trust basic tools, it is very poor manners to badmouth things without any evidence of a problem.
There was no bad mouthing, and no reference in my post to anything about you. My recommendation was about not trusting complex (remote) GUI tools, when simple (local) tools could be used for simple, precise work.
Nslookup is *NOT* broken.
... thereby declaring yourself to be NON expert in DNS. nslookup is broken, has been for years. This is widely known, documented, is ancient history. It was broken before MS included it in NT4. The nslookup delivered with BIND was fixed a long time ago. MS's is still broken.
Specifically, if the PTR for the DNS being used does not exist, (MS) nslookup fails the DNS query with "host not found". nslookup requires stupidly, brokenly a PTR for the NS used. The error message leads people to believe the domain name of their query was not found, when in fact nslookup is broken and is giving spurious errors.
You just hate it
Stop mind-reading, your are really bad at it.
I dislike any tool that does not work correctly.
because it doesn't display the information that dig displays
wrong. nslookup gives erroneous results.
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/
