I would suggest using DIG for
DNS lookups/troubleshooting.
Very powerful and returns more information.
DIG output:
Code:
U:\>dig www.unix.com
; <<>> DiG 9.3.1 <<>> www.unix.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 80
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 5
;; QUESTION SECTION:
;www.unix.com. IN A
;; ANSWER SECTION:
www.unix.com. 120 IN A 81.17.242.186
;; AUTHORITY SECTION:
unix.com. 381 IN NS ns1.sitelutions.com.
unix.com. 381 IN NS ns5.sitelutions.com.
unix.com. 381 IN NS ns2.sitelutions.com.
unix.com. 381 IN NS ns4.sitelutions.com.
unix.com. 381 IN NS ns3.sitelutions.com.
;; ADDITIONAL SECTION:
ns1.sitelutions.com. 170479 IN A 66.117.40.216
ns2.sitelutions.com. 170479 IN A 69.26.176.28
ns3.sitelutions.com. 170480 IN A 66.231.180.140
ns4.sitelutions.com. 170480 IN A 69.26.176.208
ns5.sitelutions.com. 31857 IN A 69.93.94.154
;; Query time: 406 msec
;; SERVER: <hidden>
;; WHEN: Wed Feb 11 12:36:01 2009
;; MSG SIZE rcvd: 228
