Troubleshooting Domain DNS issues.

Example troubleshooting steps in resolving your network/DNS connection.

vector:/~
vector:$ traceroute -n -w 2 -q 2 -m 30 4.2.2.2
traceroute to 4.2.2.2 (4.2.2.2), 30 hops max, 60 byte packets
1 218.248.84.10 100.556 ms 319.220 ms
2 10.42.43.97 290.287 ms 291.111 ms
3 10.42.43.28 339.076 ms 340.995 ms
4 172.24.7.214 339.961 ms *
5 209.58.33.133 590.822 ms 589.914 ms
6 64.86.252.45 658.764 ms 660.691 ms
7 4.68.62.117 661.651 ms 662.608 ms
8 4.69.144.3 664.563 ms 4.69.144.67 663.506 ms
9 4.2.2.2 564.279 ms 548.440 ms
vector:/~
vector:$

If you are on a windows box, try tracert -d 4.2.2.2

vector:/~
vector:$ nslookup -debug mit.edu 4.2.2.2
Server: 4.2.2.2
Address: 4.2.2.2#53

------------
QUESTIONS:
mit.edu, type = A, class = IN
ANSWERS:
-> mit.edu
internet address = 18.9.22.69
ttl = 60
AUTHORITY RECORDS:
ADDITIONAL RECORDS:
------------
Non-authoritative answer:
Name: mit.edu
Address: 18.9.22.69

vector:/~
vector:$ dig @4.2.2.2 mit.edu

; <<>> DiG 9.7.3-P1 <<>> @4.2.2.2 mit.edu
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 343
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;mit.edu. IN A

;; ANSWER SECTION:
mit.edu. 26 IN A 18.9.22.69

;; Query time: 388 msec
;; SERVER: 4.2.2.2#53(4.2.2.2)
;; WHEN: Mon Jan 9 14:41:43 2012
;; MSG SIZE rcvd: 41

vector:/~
vector:$