I'm not sure if this is new or not, but if you only want to use one machine for serving DNS, you should easily be able to just assign another IP to that machine.
We've done that for over three years now, and it's been working nicely *so far* Of course, redundancy is better than evil workarounds like this, but if you don't have enough resources to throw at a problem, sneaky solutions always help ;) / oscar rylin mgon international ab -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Tom Brown Sent: den 4 september 2002 23:00 To: [EMAIL PROTECTED] Subject: is there No longer a requirement for unique hostname - IP pairs [root@americium ~]# whois 209.249.251.98 [whois.internic.net] Whois Server Version 1.3 Domain names in the .com, .net, and .org domains can now be registered with many different competing registrars. Go to http://www.internic.net for detailed information. DNS1.PMC2K.COM NS1.DOMAIN-DNS.COM if you do a whois on PMC2K.COM and DOMAIN-DNS.COM (which is ours), you'll see they have the same IP addresses for dns servers, which at least until recently wasn't allowed. Host records had to have unique IP addresses. I know verisign was supposed to be working on removing this restriction.... My question is, is this new (the ability to specify new names for old IP addresses)? Is this example a bug? We can make great use of this if we can count on it being there... on the other hand it is less publicity for our domain-dns.com service :-( ---------------------------------------------------------------------- [EMAIL PROTECTED] | Always bear in mind that your own resolution to http://BareMetal.com/ | success is more important than any other one web hosting since '95 | thing. - Abraham Lincoln
