Yahoo DNS broken?

Matthew Petach mpetach at netflight.com
Wed Dec 3 15:16:13 CST 2008


On 12/3/08, Paul Stewart <pstewart at nexicomgroup.net> wrote:
> 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.

>
>
>  -----Original Message-----
>  From: Nathan Ward [mailto:nanog at daork.net]
>  Sent: Wednesday, December 03, 2008 3:41 PM
>  To: nanog list
>  Subject: Re: Yahoo DNS broken?
>
>  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
>
>  On 4/12/2008, at 9:36 AM, Larry Daberko wrote:
>
>  > 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 :-)
>  >
>  > -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
>  >
>  >
>  >
>  > !DSPAM:22,4936edf127844578318734!
>  >
>  >
>
>  --
>  Nathan Ward
>
>
>
>
>
>
>
>
>
>
> ----------------------------------------------------------------------------
>
>  "The information transmitted is intended only for the person or entity to which it is addressed and contains confidential and/or privileged material. If you received this in error, please contact the sender immediately and then destroy this transmission, including all attachments, without copying, distributing or disclosing same. Thank you."
>
>




More information about the NANOG mailing list