>>>>> "Patrick" == Patrick Goetz <[EMAIL PROTECTED]> writes:
Patrick> The problem has nothing to do with your ISP and
Patrick> everything to do with the general lethargy and sloth of
Patrick> Network Solutions, the outfit that controls exactly when
Patrick> your domain will start to resolve. Nothing you (or your
Patrick> ISP) do locally will have any affect until they work
Patrick> their magic upstairs.
Ok, now I'm confused. :)
1. I registered this domain with domainmonger.com, not NSI. How does
NSI fit in this picture?
2. I thought that running nslookup on my domain and its primary
nameserver would completely avoid anyone's "sloth" (with the
exception of possible problems on granitecanyon's end, of course.)
How would NSI's slowness effect the fact that my own primary and
secondary nameservers don't seem to see my changes?
Also, as previously stated, the output of nslookup on ns1 is a bit
odd. It even seems to spit out data for invalid domains. As an example,
check out the following nslookup queries on my local DNS and on ns1:
ethereal:~> nslookup www.slashdot.org
Server: localhost
Address: 127.0.0.1
Non-authoritative answer:
Name: slashdot.org
Address: 64.28.67.48
Aliases: www.slashdot.org
ethereal:~> nslookup thisoneprobablydoesntexist.com
Server: localhost
Address: 127.0.0.1
*** localhost can't find thisoneprobablydoesntexist.com: Non-existent host/domain
ethereal:~> nslookup www.slashdot.org ns1.granitecanyon.com
Server: ns1.granitecanyon.com
Address: 205.166.226.38
Name: www.slashdot.org.
Served by:
- A.ROOT-SERVERS.NET
198.41.0.4
org
- G.ROOT-SERVERS.NET
192.112.36.4
org
- F.GTLD-SERVERS.NET
198.17.208.67
org
- F.ROOT-SERVERS.NET
192.5.5.241
org
- E.ROOT-SERVERS.NET
192.203.230.10
org
- J.GTLD-SERVERS.NET
198.41.0.21
org
- K.GTLD-SERVERS.NET
195.8.99.11
org
- A.GTLD-SERVERS.NET
198.41.3.38
org
- M.GTLD-SERVERS.NET
210.176.152.18
org
- H.GTLD-SERVERS.NET
216.33.75.82
org
ethereal:~> nslookup thisoneprobablydoesntexist.com ns1.granitecanyon.com
Server: ns1.granitecanyon.com
Address: 205.166.226.38
Name: thisoneprobablydoesntexist.com.
Served by:
- A.ROOT-SERVERS.NET
198.41.0.4
com
- G.ROOT-SERVERS.NET
192.112.36.4
com
- F.GTLD-SERVERS.NET
198.17.208.67
com
- F.ROOT-SERVERS.NET
192.5.5.241
com
- E.ROOT-SERVERS.NET
192.203.230.10
com
- J.GTLD-SERVERS.NET
198.41.0.21
com
- K.GTLD-SERVERS.NET
195.8.99.11
com
- A.GTLD-SERVERS.NET
198.41.3.38
com
- M.GTLD-SERVERS.NET
210.176.152.18
com
- H.GTLD-SERVERS.NET
216.33.75.82
com
So, I'm wondering if nslookup on ns1 shouldn't be trusted? I tried ns2
and the results are somewhat more sane:
ethereal:~> nslookup www.slashdot.org ns2.granitecanyon.com
Server: ns2.granitecanyon.com
Address: 209.166.62.198
Name: slashdot.org
Address: 64.28.67.48
Aliases: www.slashdot.org
ethereal:~> nslookup nolansown.com ns2.granitecanyon.com
Server: ns2.granitecanyon.com
Address: 209.166.62.198
*** ns2.granitecanyon.com can't find nolansown.com: Server failed
But, my own domain isn't even resolving on its own secondary
nameserver?
Anyhow, sorry if I seem to be a bit paranoid; at this point I'm not
necessarily interested in my domain resolving, but I'd at least like
to have some assurances that I've set up my zone configuration
correctly. I had thought that the above methods would have
circumvented any propagation delays, but apparently something else
isn't right.
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
