changing nameservers - NS records

[Kevin Darcy]

"BLINCO, Ken" wrote:

> Hi,
>
> This is not really a bind question - but more a dns question (hope that's
> ok)
>
> If a domain name (e.g. domain.com.au) is registered with the following
> details:
>
> domain.com.au
> nameserver: nameserver1.domain.com.au
> nameserver ip:  203.10.10.10.
>
> The host nameserver1.domain.com.au sits on in our dmz with the ip
> 203.10.10.10.  Suppose we wanted to replace this nameserver with a new
> machine.  This machine needs to be called nameserver2.domain.com.au (for
> other reasons).  During the cutover period, would there be a problem if we
> just changed uplugged namerserver1.domain.com.au and gave
> nameserver2.domain.com.au the ip address 203.10.10.10?
>
> As far as routing of requests is concerned, it should be fine.  What I'm
> concerned about is whether the fact that the hostname and the NS record for
> domain.com.au in the zone files being served is now nameserver2 rather than
> nameserver1.  The delegation record states nameserver1 has the authoritative
> nameserver.  Will this affect how queries from the Internet are handled?

The NS records you publish in the zone should match the NS records in the delegation, but there's no particular reason, from a DNS perspective, why either should have to match what is set as the "hostname" or "node name" of the box on which the nameserver runs. Applications, on the other hand, may care whether there is a consistency
between those names....

                                                                                                                                                    - Kevin