Sunday, November 16, 2008
Verizon.net DNS Server Issues with Yahoo
Verizon DSL's DNS servers are not seeing yahoo.com for some reason. I had to change my DNS settings to opendns.com's to solve the issue. Here's the dig results:
dig @4.2.2.2 finance.yahoo.com
; <<>> DiG 9.5.0-P2 <<>> @4.2.2.2 finance.yahoo.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 43002
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;finance.yahoo.com. IN A
;; Query time: 33 msec
;; SERVER: 4.2.2.2#53(4.2.2.2)
;; WHEN: Sun Nov 16 11:04:37 2008
;; MSG SIZE rcvd: 35
But 4.2.2.1 works:
dig @4.2.2.1 finance.yahoo.com
; <<>> DiG 9.5.0-P2 <<>> @4.2.2.1 finance.yahoo.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45789
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;finance.yahoo.com. IN A
;; ANSWER SECTION:
finance.yahoo.com. 21600 IN CNAME finance.yahoo6.akadns.net.
finance.yahoo6.akadns.net. 60 IN A 216.252.99.134
;; Query time: 56 msec
;; SERVER: 4.2.2.1#53(4.2.2.1)
;; WHEN: Sun Nov 16 11:26:42 2008
;; MSG SIZE rcvd: 90
After changing to opendns.com's nameservers:
dig finance.yahoo.com
; <<>> DiG 9.5.0-P2 <<>> finance.yahoo.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45677
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;finance.yahoo.com. IN A
;; ANSWER SECTION:
finance.yahoo.com. 19161 IN CNAME finance.yahoo6.akadns.net.
finance.yahoo6.akadns.net. 22 IN A 216.252.106.49
;; Query time: 75 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Nov 16 11:05:01 2008
;; MSG SIZE rcvd: 90
It seems that Verizon changed their nameservers for their ISP customers from 4.2.2.2 and 4.2.2.1 to 131.25.21.14 and 131.25.22.14. Here's the whois for verizon.net. There are four primary DNS servers - two for Bell Atlantic and two for GTE. I'll just stick with opendns.com. At least there won't be so much confusion when my ISP changes something important without notifying the customer or the owners of the DNS root servers for the .net domain.
dig @4.2.2.2 finance.yahoo.com
; <<>> DiG 9.5.0-P2 <<>> @4.2.2.2 finance.yahoo.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 43002
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;finance.yahoo.com. IN A
;; Query time: 33 msec
;; SERVER: 4.2.2.2#53(4.2.2.2)
;; WHEN: Sun Nov 16 11:04:37 2008
;; MSG SIZE rcvd: 35
But 4.2.2.1 works:
dig @4.2.2.1 finance.yahoo.com
; <<>> DiG 9.5.0-P2 <<>> @4.2.2.1 finance.yahoo.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45789
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;finance.yahoo.com. IN A
;; ANSWER SECTION:
finance.yahoo.com. 21600 IN CNAME finance.yahoo6.akadns.net.
finance.yahoo6.akadns.net. 60 IN A 216.252.99.134
;; Query time: 56 msec
;; SERVER: 4.2.2.1#53(4.2.2.1)
;; WHEN: Sun Nov 16 11:26:42 2008
;; MSG SIZE rcvd: 90
After changing to opendns.com's nameservers:
dig finance.yahoo.com
; <<>> DiG 9.5.0-P2 <<>> finance.yahoo.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45677
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;finance.yahoo.com. IN A
;; ANSWER SECTION:
finance.yahoo.com. 19161 IN CNAME finance.yahoo6.akadns.net.
finance.yahoo6.akadns.net. 22 IN A 216.252.106.49
;; Query time: 75 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Nov 16 11:05:01 2008
;; MSG SIZE rcvd: 90
It seems that Verizon changed their nameservers for their ISP customers from 4.2.2.2 and 4.2.2.1 to 131.25.21.14 and 131.25.22.14. Here's the whois for verizon.net. There are four primary DNS servers - two for Bell Atlantic and two for GTE. I'll just stick with opendns.com. At least there won't be so much confusion when my ISP changes something important without notifying the customer or the owners of the DNS root servers for the .net domain.
Labels: bad DNS records
