On Wed, 4 Sep 2002, Dave Warren wrote: > > You bring up a valid point. How do we prevent people from creating ns > > host names pointing at our ns hosts? I guess we could periodically change > > the ns IP addresses and just update our authorized ns host records to use > > the new IP... hmm... > > Does having additional nameserver records pointed at your IPs actually harm > anything or cause any actual problems?
oh heck, I'll take this back to the list, since the example given is pretty classic ... And while here I will apologize for not having searched the archives, and bringing up a topic that was discussed only a few days ago. The actual ability to have multiple names point at the same nameservers is simply a capability. Whether it is good, bad, or just ugly depends on how it is used. I wrote a (possibly private) e-mail where I pointed out that the ability to hide the hosting company can be usefull (canadian hosting company, US webmaster/client, US client wants to look US and still deal with Canadian hosting service, having ns1.theirdomain and ns2.theirdomain helps hide canadian link)... However, domain-dns.com and pmc2k.com are the opposite (bad _and_ ugly). Someone is using this multiple-names-per-ip and our domain-dns.com service itself to offer their own free dns service. It is far from completely transparent, and we don't really object (the more users the better), but we would rather that the domain-dns.com name got around as compared to the dns.pmc2k.com name... anyhow, enough talk... go to http://pmc2k.com/ and take the free-dns link at the bottom of the right hand menu. note the instructions and take the link to http://dns.pmc2k.com/. Now visit http://domain-dns.com/ with dns1.pmc2k.com and dns2.pmc2k.com having the same IP addresses as ns1.domain-dns.com and ns2.domain-dns.com, it works, and provides a much stronger implication that pmc2k is actually running their own DNS service. Enough rambling, I will try to shutup now. -Tom
