At 6/8/01 3:41 PM, Jim Carey wrote: >A customer allowed his name to expire (poweredparachuting.com). The name was >then deactivated. He renewed it and the whois from geektools and opensrs >show the name with the new expiry and the whois from nsi shows the name >delegated to my nameservers - so, to me, that looks like the name should be >in an ok state.. > >Now the name is not resolving - so the question is why would that be. It is >renewed, the whois appears to be in order, NSI knows where it is to be found >, but I can't ping the name or access it via browser - the customer is >marginally distressed. It has not yet fully propagated to all of the root servers: ---- A.GTLD-SERVERS.NET: poweredparachuting.com. 2D IN NS WEB.OZDNS.NET. poweredparachuting.com. 2D IN NS WEB2.OZDNS.NET. B.GTLD-SERVERS.NET: poweredparachuting.com. 2D IN NS WEB2.OZDNS.NET. poweredparachuting.com. 2D IN NS WEB.OZDNS.NET. C.GTLD-SERVERS.NET: poweredparachuting.com. 2D IN NS WEB.OZDNS.NET. poweredparachuting.com. 2D IN NS WEB2.OZDNS.NET. D.GTLD-SERVERS.NET: E.GTLD-SERVERS.NET: poweredparachuting.com. 2D IN NS WEB2.OZDNS.NET. poweredparachuting.com. 2D IN NS WEB.OZDNS.NET. F.GTLD-SERVERS.NET: G.GTLD-SERVERS.NET: I.GTLD-SERVERS.NET: J.GTLD-SERVERS.NET: K.GTLD-SERVERS.NET: poweredparachuting.com. 2D IN NS WEB2.OZDNS.NET. poweredparachuting.com. 2D IN NS WEB.OZDNS.NET. L.GTLD-SERVERS.NET: M.GTLD-SERVERS.NET: poweredparachuting.com. 2D IN NS WEB.OZDNS.NET. poweredparachuting.com. 2D IN NS WEB2.OZDNS.NET. ----- (This is the output of a script I have that does a "dig" on each of the root servers and displays the results. It indicates the domain is not in d, f, g, i, j, or l yet.) When it's missing from this many, it means that it's still propagating. You need to wait a little longer until it is entered in all of them. It appears that NSI registry missed at least one root server update in the last 24 hours, because I'm seeing much longer-than-usual propagation delays, too. -- Robert L Mathews, Tiger Technologies
