Changing authoritative nameserver IPs

[Nod]

On Fri, 24 Jun 2005 12:57:56 +0000, Stephane Bortzmeyer <bortzmeyer at nic.fr>
wrote:

>On Thu, Jun 23, 2005 at 03:26:04PM +0000,
> Nod <none at nospam.none> wrote 
> a message of 14 lines which said:
>
>> The change has already propogated to the root nameservers,
>
>It is very unlikely that your nameservers are known to the root
>nameservers, unless you manage a TLD (top-level domain). So, I
>seriously doubt that information.
I might be explaining what I mean poorly. If that's the case, please correct me.
This is what I'm referring to, as an example:

Server:  b.gtld-servers.net
Addresses:  192.33.14.30, 2001:503:231d::2:30

Non-authoritative answer:
dotster.com     nameserver = ns1.dotster.com
dotster.com     nameserver = ns2.dotster.com

Authoritative answers can be found from:
ns1.dotster.com internet address = 64.94.117.199
ns2.dotster.com internet address = 63.251.83.78

The root nameservers know the IPs of ns1.dotster.com and ns2.dotster.com, no? Is
gtld-servers.net (refferred from root-servers.net) not a root of its own? This
is the change I'm referring to. I don't control any TLDs, just a .net in this
case.

>
>> however, domains registered with some of the other registrars
>> currently are returning the old IP via whois.
>
>This is expected. For "thin" registries like ".com", there is no
>synchronization of the data between the registrars (that's the purpose
>of thin registries).
Anything that I should expect to be broken as a result of the whois data not
matching the auth-NS IP? I control both IPs in question, I merely needed to
separate my auth NS from my caching NS.

>> Is there a policy in place, essentially requiring the various
>> registrars to re-sync their whois data with the root nameserver
>> data?
>
>Again, certainly not with the root.
>