At 11/7/02 1:33 AM, George Kirikos wrote: >If we already have a nameserver, say at ns1.domain1.com, do we need to >do anything special in the configuration of the physical nameserver, if >we simply create a new nameserver record of ns1.domain2.com and point >it at that IP address, e.g. for vanity? (e.g. if one has DNS hosting at >UltraDNS, with nameservers: > >udns1.ultradns.net 204.69.234.1 >udns2.ultradns.net 204.74.101.1 > >and we simply create a 'vanity' privately-branded nameserver instead >of: > >ns1.company.com 204.69.234.1 >ns2.company.com 204.74.101.1 > >would that "work", without having to notify UltraDNS (i.e. is the >hostname used at all, or just purely the IP address?; for webhosting, >the hostname is used, e.g. name-based hosts in http 1.1)
While it will "work" at first, it will stop working when ultradns.net changes the IP address of their nameservers without telling you about it. And by the time you notice, you'll be screwed: it'll take you 48 hours or more of downtime to update the roots and recover from it. The reason hosts are registered as nameservers is precisely so that the owner of that nameserver can move it to a new IP address without having to notify the owner of each domain using that nameserver. If you set up a different name for it, you break the link. Now, if you controlled the host records for both the original nameserver and the vanity nameservers, and you remembered to update them all at the same time when you changed IP addresses, that would be okay. ------------------------------------ Robert L Mathews, Tiger Technologies
