At 11/11/01 9:17 AM, Charles Daminato wrote: >For the gTLD registry, simply renaming the host in your management profile >will affect the change (usual propogation time) - both domains must be in >the same profile. We've done this before with some folks, and it's >seamless. > >As for other TLDs, you'll have to update them all here and there since >they all hold a local system for referencing nameservers by name (if you >were simply updating the IPs, most registries would pick up on that)
OK, thanks. Hmmmm.... so domains under, say, .tv, would still point at the old names, huh? But I can solve that problem by making my authoritative servers respond correctly to lookups for the old names forever, because the non-gTLD roots don't use glue records if the nameserver is under a gTLD zone, so they'll query the nameservers of the old nameserver's zone for the address. So, let's say example.cc still lists ns1.tigertech.com as a nameserver, even though I changed the name of it to ns1.tigertech.net. That will be okay as long as the authoritative nameservers for tigertech.com (which will then include ns1.tigertech.net) correctly answer to lookups for ns1.tigertech.com indefinitely, even though the com zone no longer contains a glue record for ns1.tigertech.com -- when the resolver is trying to find the addresses of authoritative nameservers for example.cc, it'll just have to do an extra lookup to get the answer from my nameservers instead of having it spoon-fed from the com zone's glue record. Common sense tells me to test this on a fake nameserver before doing it to customer domains. I'll report back to the list when and if I actually do this. -- Robert L Mathews, Tiger Technologies
