Domain not propagating

[Kevin Darcy]

You're right -- NSI only shows those two nameservers in its WHOIS. But what
really matters is what the "com" servers think, and they're giving out
register.com delegation records. I wonder if someone tried to register the
same domain name with register.com and somehow there was a registry snafu that
caused the register.com nameservers to be added to the delegations in addition
to the ones in NSI's WHOIS database(?) In any case, you'll have to deal with
NSI (at least initially) to get those nameservers out of your delegations. Or
maybe you could talk nicely to register.com and have them become slaves for
the zone for free (?) (Fat chance).


- Kevin

John Cesta wrote:

> Domain servers in listed order:
>
>    DNS.LOOKWWW.COM  207.234.248.35
>    NS2.PRIMARYDNS.COM  216.219.239.8
>
> "Michael Kjorling" <michael at kjorling.com> wrote in message
> news:9h261c$4ok at pub3.rc.vix.com...
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > This looks like a delegation problem to me. Looking it up using dig
> > produces this:
> >
> > ; <<>> DiG 9.1.2 <<>> shopartmart.com. ns
> > ;; global options:  printcmd
> > ;; Got answer:
> > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52810
> > ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 4
> >
> > ;; QUESTION SECTION:
> > ;shopartmart.com.               IN      NS
> >
> > ;; ANSWER SECTION:
> > shopartmart.com.        172800  IN      NS      DNS18.REGISTER.com.
> > shopartmart.com.        172800  IN      NS      DNS.LOOKWWW.com.
> > shopartmart.com.        172800  IN      NS      NS2.PRIMARYDNS.com.
> > shopartmart.com.        172800  IN      NS      DNS17.REGISTER.com.
> >
> > ;; ADDITIONAL SECTION:
> > DNS.LOOKWWW.com.        172800  IN      A       207.234.248.35
> > NS2.PRIMARYDNS.com.     172800  IN      A       216.219.239.8
> > DNS17.REGISTER.com.     172800  IN      A       209.67.50.247
> > DNS18.REGISTER.com.     172800  IN      A       209.67.50.248
> >
> > ;; Query time: 188 msec
> > ;; SERVER: 127.0.0.1#53(0.0.0.0)
> > ;; WHEN: Sat Jun 23 15:04:36 2001
> > ;; MSG SIZE  rcvd: 201
> >
> > dns17.register.com. and dns18.register.com. resolves shopartmart.com.
> > to 209.67.50.203
> > dns.lookwww.com. and ns2.primarydns.com. resolves it to 216.219.239.8
> >
> > So, Register.com still considers themselves authorative (aa set), and
> > the domain is pointed to both your and Register.com's name servers.
> > Statistically speaking, you should get the answer pointing to
> > Register.com in 50% of the cases, assuming no caching of that invalid
> > response.
> >
>
> Yes, that's the way it works. 50-50 . A whois at networksolutions.com
> produces this:
>
> Domain servers in listed order:
>
>    DNS.LOOKWWW.COM  207.234.248.35
>    NS2.PRIMARYDNS.COM  216.219.239.8
>
> A whois at nsiregistry.com produces this:
>
> Domain Name: SHOPARTMART.COM
>    Registrar: NETWORK SOLUTIONS, INC.
>    Whois Server: whois.networksolutions.com
>    Referral URL: http://www.networksolutions.com
>    Name Server: DNS.LOOKWWW.COM
>    Name Server: NS2.PRIMARYDNS.COM
>    Name Server: DNS17.REGISTER.COM
>    Name Server: DNS18.REGISTER.COM
>    Updated Date: 16-dec-2000
>
> So, at the make changes screen at netsol there is nothing to change. It
> seems to be fouled up in there somewhere. I'll give them a call on Monday.
>
> Thanks to everyone who provided something more for me to work with!
>
> John Cesta
>
> > Having Register.com get their DNS servers out of the delegation
> > information should solve the problem.
> >
> >
> > Michael Kjörling
> >
> >
> > On Jun 22 2001 16:19 -0400, John Cesta wrote:
> >
> > > We host about 300 domains. All the zone files are configured
> automagically
> > > so they are all identical in format. All the domains on our server run
> > > properly except one. We had a customer register a domain called:
> > > shopartmart.com  Our DNS  zones seem to be correct. The domain is
> registered
> > > with Internic and DNS are properly pointing to us and our secondary.
> > > However, the domain, when entered into a browser resolves to
> registrar.com
> > >
> > > I cannot figure this out, the domain resolves properly from my
> workstation
> > > and other PCs I've been in front of, and, from some other countries I
> tried
> > > at geektools.com
> > >
> > > The domain, however, resolves to registrar.com when entered into an AOL
> > > connection and a bellsouth connection and other ISPs.
> >
> > - --
> > Michael Kjörling - michael at kjorling.com - PGP: 8A70E33E
> > "We must be the change we wish to see" (Mahatma Gandhi)
> >
> > ^..^     Support the wolves in Norway -- go to     ^..^
> >  \/   http://home.no.net/ulvelist/protest_int.htm   \/
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.0.6 (GNU/Linux)
> > Comment: For info see http://www.gnupg.org
> >
> > iD8DBQE7NJWtKqN7/Ypw4z4RApt9AJ9gtGTX+csJDYHBggXxk1RAuMfpHQCfWiC2
> > 13KmHeGbcSYxJ3H7TzGXRws=
> > =0Tzj
> > -----END PGP SIGNATURE-----
> >
> >
> >
> >