In
Mike said:
I have an AD integrated DNS server setup and I want to ad
an additional DNS server. The new server is not a DC
like my Primary DNS server. Is it really as simple as
following the wizard and selecting Standard Secondary,
plugging in the domain and I am done. Can someone point
me in the right direction. Does anyone know of a doc
that explains this?
Thanks.....
It is almost that simple, before you can transfer the zone data to the
secondary, first go to the zone properties on the primary, Zone Transfer
tab, set allow zone transfers to all IP addresses on the secondary DNS
machine. If both servers are behind the same NAT device, remember that the
Primary will see the secondary on the machine's private addresses so you
most likely cannot use "Allow zone transfers to the name servers on the Name
Server tab" (Default). You may also want add an NS record for the
secondary's host name. If you don't create an NS record for the Secondary,
you will need to use the "Notify" option also on the Zone Transfer tab, in
that case select "Notify the following servers" and put in the Secondary's
private address if behind the same NAT device or public address if the
Secondary is not behind the same NAT device. If you don't use the notify
option the name servers will use the refresh, retry, and expire values for
getting zone transfers.
Zone transfers will fail if you do not select the right IP address because
the Primary will only allow zone transfers to the IP address it (the
Primary) sees the zone transfer request coming from.
If the secondary will be getting zone transfers from a zone with dynamic
updates, you will begin to get runtime events on the Secondary DNS event
log, this is due to the incremental zone transfers for the all the dynamic
records. You can ignore these as long as the zone transfers are successful.
