> Anyone who thinks it's okay to have all your name servers in the
> same place should review the outage Microsoft had a few months ago.
While I do agree with this (don't do an NS lookup on vpop.net ;-) )
I don't think this has to do with the original question, which was:
Can I map multiple nameservers to a single IP address?
What if you wanted to offer your customers "virtual nameserver"
service, so that:
NS1.WEBHOST.COM: 1.2.3.4
NS2.WEBHOST.COM: 1.3.4.5
and
NS1.CUSTOMER.COM: 1.2.3.4
NS2.CUSTOMER.COM: 1.3.4.5
Can't do it in COM/NET/ORG. You gotta burn IP#'s which is what
we do in the rare case that a customer wants to look really cool.
Also, a single IP does not neccessarily map to a single location.
If you put your servers in an anycast group, a single IP can map
to multiple physical locations and theoretically the client would
get to the closest one that is up. I believe a few large dns
providers are using anycast now.
Re: wanting to have only 1 nameserver answering for a zone, I can
envision a few specialized apps that may want that. For instance,
if you run your app on the same box that provides dns, you let the
the client know ASAP that the service is unavailable. If the client
can go to another nameserver and resolve you, and then find out that
you're down, you may have wasted a second of time or so...
regards,
-joe
