Yahoo DNS broken?

Mailman List Mirror (Read Only)
1

I am unable to resolve www.yahoo.com. Tracing DNS back from the root
servers shows that www.yahoo.com is a CNAME to www.wa1.b.yahoo.com and
there are no A records for that hostname.

Anyone have more details or a Yahoo contact? I'm unable to get to their
webpage as it is :slight_smile:

-Larry Daberko
iServe Technologies

$ dig @ns1.yahoo.com www.yahoo.com

; <<>> DiG 9.4.2 <<>> @ns1.yahoo.com www.yahoo.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56431
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;www.yahoo.com. IN A

;; ANSWER SECTION:
www.yahoo.com. 300 IN CNAME www.wa1.b.yahoo.com.

;; AUTHORITY SECTION:
wa1.b.yahoo.com. 300 IN NS yf1.yahoo.com.
wa1.b.yahoo.com. 300 IN NS yf2.yahoo.com.

;; ADDITIONAL SECTION:
yf1.yahoo.com. 1800 IN A 68.142.254.15
yf2.yahoo.com. 1800 IN A 68.180.130.15

;; Query time: 15 msec
;; SERVER: 68.180.131.16#53(68.180.131.16)
;; WHEN: Wed Dec 3 15:34:09 2008
;; MSG SIZE rcvd: 123

but looking up the host itself gives no answer

$ dig @ns1.yahoo.com www.wa1.b.yahoo.com

; <<>> DiG 9.4.2 <<>> @ns1.yahoo.com www.wa1.b.yahoo.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34875
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;www.wa1.b.yahoo.com. IN A

;; AUTHORITY SECTION:
wa1.b.yahoo.com. 300 IN NS yf1.yahoo.com.
wa1.b.yahoo.com. 300 IN NS yf2.yahoo.com.

;; ADDITIONAL SECTION:
yf1.yahoo.com. 1800 IN A 68.142.254.15
yf2.yahoo.com. 1800 IN A 68.180.130.15

;; Query time: 15 msec
;; SERVER: 68.180.131.16#53(68.180.131.16)
;; WHEN: Wed Dec 3 15:35:07 2008
;; MSG SIZE rcvd: 105

2

Their other pages (finance.yahoo.com) and such seem to resolve ok.

Wondering if it isn't part of a bigger problem because I got a complaint
that many sites
Were unreachable for a bit.

Chuck

Charles L. Mills
Senior Network Engineer
Access Data Corporation / Pittsburgh, PA 15238
(412) 968-4024 / FAX: (412) 967-9504
cmills@accessdc.com / http://www.accessdc.com
Hosting, Colocation, D-R and Managed Services

3

There is no A records, correct.
There is a CNAME though:
www.wa1.b.yahoo.com. 45 IN CNAME www-real.wa1.b.yahoo.com.
www-real.wa1.b.yahoo.com. 45 IN A 209.131.36.158

4

Seems to be back up now.

5

Yes, www.yahoo.com is unreachable for me too, but mail.yahoo.com and
login.yahoo.com are up.

6

I am unable to resolve www.yahoo.com. Tracing DNS back from the root
servers shows that www.yahoo.com is a CNAME to www.wa1.b.yahoo.com and
there are no A records for that hostname.

Anyone have more details or a Yahoo contact? I'm unable to get to their
webpage as it is :slight_smile:

-Larry Daberko
iServe Technologies

$ dig @ns1.yahoo.com www.yahoo.com
; <<>> DiG 9.4.2 <<>> @ns1.yahoo.com www.yahoo.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56431
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;www.yahoo.com. IN A
;; ANSWER SECTION:
www.yahoo.com. 300 IN CNAME www.wa1.b.yahoo.com.
;; AUTHORITY SECTION:
wa1.b.yahoo.com. 300 IN NS yf1.yahoo.com.
wa1.b.yahoo.com. 300 IN NS yf2.yahoo.com.
;; ADDITIONAL SECTION:
yf1.yahoo.com. 1800 IN A 68.142.254.15
yf2.yahoo.com. 1800 IN A 68.180.130.15
;; Query time: 15 msec
;; SERVER: 68.180.131.16#53(68.180.131.16)
;; WHEN: Wed Dec 3 15:34:09 2008
;; MSG SIZE rcvd: 123

but looking up the host itself gives no answer

; <<>> DiG 9.4.2 <<>> @ns1.yahoo.com www.wa1.b.yahoo.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34875
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;www.wa1.b.yahoo.com. IN A
;; AUTHORITY SECTION:
wa1.b.yahoo.com. 300 IN NS yf1.yahoo.com.
wa1.b.yahoo.com. 300 IN NS yf2.yahoo.com.
;; ADDITIONAL SECTION:
yf1.yahoo.com. 1800 IN A 68.142.254.15
yf2.yahoo.com. 1800 IN A 68.180.130.15

Well, since ns1.yahoo.com isn't authoritative for wa1.b.yahoo.com, then I wouldn't expect it to have the answer. Trying yf1.yahoo.com:

> dig www.wa1.b.yahoo.com. @yf1.yahoo.com

; <<>> DiG 9.4.2-P1 <<>> www.wa1.b.yahoo.com. @yf1.yahoo.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31055
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;www.wa1.b.yahoo.com. IN A

;; ANSWER SECTION:
www.wa1.b.yahoo.com. 60 IN CNAME www-real.wa1.b.yahoo.com.
www-real.wa1.b.yahoo.com. 60 IN A 209.131.36.158

;; Query time: 3 msec
;; SERVER: 68.142.254.15#53(68.142.254.15)
;; WHEN: Wed Dec 3 12:55:24 2008
;; MSG SIZE rcvd: 76

It's a chain of CNAME records, which isn't very nice, but isn't technically illegal. In most cases, it's resolvable. Not what I would do for a globally-reachable revenue-generating service, but I am sure they have their reasons.

michael

7

www.yahoo.com seems to be a CNAME for wa1.b.yahoo.com and delegated to ...

;; Received 201 bytes from 192.41.162.30#53(L.GTLD-SERVERS.NET) in 39 ms

www.yahoo.com. 300 IN CNAME www.wa1.b.yahoo.com.
wa1.b.yahoo.com. 300 IN NS yf1.yahoo.com.
wa1.b.yahoo.com. 300 IN NS yf2.yahoo.com.
;; Received 123 bytes from 68.180.131.16#53(ns1.yahoo.com) in 27 ms

% host yf1.yahoo.com
yf1.yahoo.com has address 68.142.254.15

Neither yf1.yahoo.com nor yf2 are responding to queries for me, but I can reach them

0[granite]% time host wa1.b.yahoo.com 68.142.254.15
;; connection timed out; no servers could be reached
0.002u 0.000s 0:10.00 0.0% 0+0k 0+0io 0pf+0w
1[granite]%

% ping -c 1 yf1.yahoo.com
PING yf1.yahoo.com (68.142.254.15): 56 data bytes
64 bytes from 68.142.254.15: icmp_seq=0 ttl=56 time=28.282 ms

--- yf1.yahoo.com ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/stddev = 28.282/28.282/28.282/0.000 ms

         ---Mike

8

Interesting, as my nslookup..

www.yahoo.com

Server: ns1.hostremote.net
Address: 66.187.130.31

Non-authoritative answer:
Name: www.yahoo-ht3.akadns.net
Address: 209.191.93.52
Aliases: www.yahoo.com

And yes, I can hit http://www.yahoo.com in a web browser. Works for me.

-Kyle

9

Looks like some of akamai's nameservers have misplaced themselves and yahoo.

cheers!

10

I talked to Yahoo! NOC a little while ago and they are working on the
issue - definitely DNS related and appears to possibly be east coast
only.... details are vague but they are aware of it and no ETA yet...

Paul

11

It's working for me on my Verizon FIOS connection. Is it yet another
geolocation issue?

My yahoo resolves to www.yahoo-ht3.akadns.net 209.191.93.52

Ed

12

Yes, I am now seeing the akadns.net address. Looks like went through
some fluctuation there, but the site is back up for me now. There is
also a report on the outages list.

-Larry Daberko

13

Yes, I did nslookup and got responses but wouldn't come up in my
browser, also to add it seems to be working now.

14

I talked to Yahoo! NOC a little while ago and they are working on the
issue - definitely DNS related and appears to possibly be east coast
only.... details are vague but they are aware of it and no ETA yet...

Paul

Yes; actively being worked on; Juniper T1600 went kablooie,
and when it went away, anycasted DNS went haywire as well;
still digging into it more; yes, this is primarily affecting traffic
coming through Ashburn, VA. No, I don't have an answer on
specifically what happened; yes, we're aware of the issue and
have put workarounds in place; you should be back up and
functional for the moment, though not in an optimal state.

Matt

And no, I'm not speaking authoritatively for anything or anyone
at the moment, so treat this with a few grains of salt.

15

Can someone from Akamai report as to what happened? I did not see any notice on EdgeControl but I did get email from my auto-alerts set up at Akamai as follows: