Arshad: At this point let me say that I'm trying to understand what you're seeing, but I doubt that I'll get you to an answer. What you are describing is quite puzzling. Arshad Mahmood wrote: > > On Mon, 28 Aug 2000, Glynn Clements wrote: > > > > Arshad Mahmood wrote: > > > > > My DNS can not resolve the following domain > > > passport.com > > > > It looks like Microsoft has misconfigured it again[1]. DNS says that > > hotmail.passport.com is served by ns1.hotmail.com and ns3.hotmail.com, > > but querying these servers directly reveals that ns1 isn't claiming > > authority whilst ns3 is. I'm sorry. I haven't seen this anywhere. Both nslookup, run locally against a variety of different servers, or http://dns411.com/cgi-bin/whois.pl essentially return "Domain servers in listed order: DNS4.CP.MSFT.NET 207.46.138.11; DNS5.CP.MSFT.NET 207.46.138.12" But not to quibble.. > If we run nslookup then for passport.com > > > set q=ns > > passport.com > Server: ns1-isb.sdnpk.org > Address: 203.135.2.55 > > Non-authoritative answer: > passport.com nameserver = DNS4.CP.MSFT.NET > passport.com nameserver = DNS5.CP.MSFT.NET > > Authoritative answers can be found from: > DNS4.CP.MSFT.NET internet address = 207.46.138.11 > DNS5.CP.MSFT.NET internet address = 207.46.138.12 I get exactly the same results, whether using my local nameserver, or yours, or a nameserver through worldnet.att.net > > When I traceroute to DNS4.CP.MSFT.NET then > > 12 194.ATM4-0.GW3.SEA1.ALTER.NET (146.188.201.29) 348.981 ms * 347.277 ms > 13 157.130.177.154 (157.130.177.154) 389.490 ms * * > 14 207.46.129.14 (207.46.129.14) 397.272 ms * * > 15 * * * > 16 * * * > 17 * * * > 18 * * * This is very interesting. When I do a traceroute, I get where we are wanting to go, and when I look at your results, you're getting one hop away before it goes dead. The next hop after 207.46.129.14 is dns5.cp.msft.net at 207.46.138.12 -- this seems *very* odd. > > server DNS4.CP.MSFT.NET > Default Server: DNS4.CP.MSFT.NET > Address: 207.46.138.11 > > > lc1.law5.hotmail.passport.com > Server: DNS4.CP.MSFT.NET > Address: 207.46.138.11 > > *** DNS4.CP.MSFT.NET can't find lc1.law5.hotmail.passport.com: No response > from server > > The above results show that DNS4.CP.MSFT.NET is down. "No response from server" parallels your traceroute: I bet you're still getting one hop away, and then nothing. I'm not sure your last statement is true; you *can* set server to DNS4.CP.MSFT.NET and it *does* respond. When I do this and try to walk back up the domain/server name series, I can get a response to "passport.com" of name: passport.com address: 207.46.198.16; when I try to add "hotmail.passport.com" suddenly DNS4 returns "can't find hotmail.passport.com: Non-existant host/domain."; when I say lc1.law5.hotmail.passport.com DNS4.CP.MSFT.NET returns "Non-authoritative answer: name: lc1.law5.hotmail.passport.com address: 209.185.243.7" > And when we type http://www.hotmail.com > > The Netscape shows > Connect: Looking up host: lc2.law5.hotmail.passport.com So Netscape is finding a reference to "lc2.law5.hotmail.passport.com", somewhere. This is not remarkable. But now we're referring to lc2.* Again, I get lc5.* > After some time netscape gives error Netscape is unable to locate the > server lc2.law5.hotmail.passport.com Please check the server name and try > again. And again, this is the baffling part. Your traceroute is getting one hop away and dies, and Netscape gives up with a shrug, probably one hop away, too.. And yet it all works, for me, and probably for millions of other people. > Any hints or any other facing this problem. Try the IP numbers in your browser! Again, lc1.* is 209.185.243.7 and lc2.* is 209.185.243.135 Can you traceroute to either of these IP's? Maybe you just want to get DNS out of the way ;-) After that, I have no idea. > Regards, > > Arshad Mahmood. Best wishes! - John -- John Sage FinchHaven, Vashon Island, WA, USA http://www.finchhaven.com/ mailto:jsage@finchhaven.com And remember: it's spelled l-i-n-u-x but it's pronounced "Linux" - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org
