Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DNS error contacting login.yahoo.com

Status
Not open for further replies.

rmarson

Programmer
Jun 8, 2001
2
GB
I do not get many DNS errors, but here is one that I get repeatedly. I have investigated it as described below and sure enough the DNS servers do not seem to be properly configured. Can anyone help?

There is a DNS error contacting the server login.yahoo.com (which is where Yahoo! sends you when you log in).

I have searched for DNS "A" records for this server and indeed there do not appear to be any.

To summarise:

* The Root Servers all point at the GTLD-Servers.

* The GTLD-Servers point at three entries:
- NS3.EUROPE.yahoo.com 217.12.4.71
- NS1.yahoo.com 204.71.200.33
- NS5.DCX.yahoo.com 216.32.74.10

* Of these, the first two just point back to the Root Servers, and the third just points back to the GTLD-Servers.

Does anyone know the IP address of login.yahoo.com and where the relevant Name Server "A" record is?
 
c:\>ping login.yahoo.com

Pinging login.yahoo.akadns.net [64.58.76.98] with 32 bytes of data:

Reply from 64.58.76.98: bytes=32 time=31ms TTL=126
Reply from 64.58.76.98: bytes=32 time=31ms TTL=126

Ping statistics for 64.58.76.98:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 31ms, Average = 31ms

Hope this helps,

Bill.
 
Thanks, Bill. But I can't succeed in pinging login.yahoo.com. I do get success if I ping login.yahoo.akadns.net or indeed 64.58.76.98.

If I do an NSLOOKUP on login.yahoo.com, it fails; but if I do NSLOOKUP on login.yahoo.akadns.net, it succeeds and tells me for free that login.yahoo.com is an alias for this server. When I have successfully done this, subsequent NSLOOKUPs on login.yahoo.com now succeed and indeed so does ping and the browser etc.

However, all this gets reset the next time I dial up and I am back to not being able to get to login.yahoo.com.

So I think this all has to do with how my system copes with alias servers. It seems ok once it gets them cached, but is not very clever at finding them in the first place. Any ideas?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top