Unable to update nameservers

[The Duke of Luxembourg]

Hello,

this has been discussed a trillion times!

This message comes from your domain registrar and has nothing to do with 
the DNS protocol or configuration. This has to do whith the database of the 
registrar and/or the registry, please contact them to get your nameserver's 
names added to their database!

Regards,

Marc

At 00:53 20.07.2004, you wrote:
>RYAN vAN GINNEKEN wrote:
>
> >I am having a problem trying to point a .com domain at my nameserver
> >when i try to update ns2.meganameservers.com to my nameserver
> >ns1.computerking.ca i get this error
> >
> >Unable to update nameservers: Command failed: unable to verify existence
> >of nameserver ns1.computerking.ca
> >
> >
> >
> >
> >>>>>>When i do a nslookup useing a remote server to look for NS records
> >>>>>>
> >>>>>>
> >for ns1.computerking.ca  i get this
> >
> >DNS server: ns1.kloth.net
> >DNS server's address: 213.133.98.149#53
> >Non-authoritative answer:
> > *** Can't find ns1.computerking.ca: No answer
> >Authoritative answers can be found from:
> >computerking.ca origin = ns1.computerking.ca.
> >mail addr = root.computerking.ca.
> >serial = 2004071802
> >refresh = 10800
> >retry = 3600
> >expire = 604800
> >minimum = 3600
> >
> >
> >
> >
> >>>>>>When i do a nslookup for computerking.ca shearhing for any records
> >>>>>>
> >>>>>>
> >i get this
> >
> >DNS server: ns1.kloth.net
> >DNS server's address: 213.133.98.149#53
> >Non-authoritative answer:
> >Name: ns1.computerking.ca
> >Address: 209.115.173.22
> >Authoritative answers can be found from:
> >computerking.ca nameserver = ns1.shoemasters.computerking.ca.
> >computerking.ca nameserver = ns1.computerking.ca.
> >
>Offhand, I don't see anything wrong with the resolution of
>ns1.computerking.ca or the computerking.ca zone. Could it be that the
>validation tool that "meganameservers.com" uses simply *assumes* that
>the delegated nameserver are in gTLDs???? Nah, nothing could be that
>stupid. Could it?
>
> >>>>>>Going through the dns & bind manual i noticed that everytime i do a
> >>>>>>
> >>>>>>
> >nslookup on my local machine it loops through my A records ???  as
> >nameservers examples below
> >
> >v22.computerking.ca > /usr/local/etc/namedb/pz #nslookup 192.168.0.1
> >Server:  v22.computerking.ca
> >Address:  192.168.0.202
> >
> >Name:    v22001.computerking.ca
> >Address:  192.168.0.1
> >
> >[Sun Jul 18] 03:11 PM [0]
> >v22.computerking.ca > /usr/local/etc/namedb/pz #nslookup 192.168.0.1
> >Server:  computerking.ca
> >Address:  192.168.0.202
> >
> >Name:    v22001.computerking.ca
> >Address:  192.168.0.1
> >
> >[Sun Jul 18] 03:11 PM [0]
> >v22.computerking.ca > /usr/local/etc/namedb/pz #nslookup 192.168.0.1
> >Server:  mail1.computerking.ca
> >Address:  192.168.0.202
> >
> >Name:    v22001.computerking.ca
> >Address:  192.168.0.1
> >
>Looks like you might have 3 different PTR records defined for
>192.168.0.202. Under those circumstances, a BIND nameserver would
>normally give out the answers in a fixed sequence so you'd see no
>"looping". Do you by any chance have "rotate" set in your /etc/resolv.conf?
>
>In any case, if you have no use for the additional PTR records, delete
>them.
>
>I doubt that this anomaly has anything to do with your other problem.
>
>
>                               - Kevin