. zone

[Bill B]

I am setting up a private dns hierarchy. will be using 2 dns servers for
redundancy. 1 primary, 1 secondary. everything is set up and running
smoothly, but i have 1 question..

Is it necessary to replicate the "." zone to the secondary dns server?
Should i just set up a primary . "zone"
Or do i even need the . zone on the secondary dns server?

thanks.

Bill

 

[Kevin D. Goodknecht Sr. [MVP]]

In Bill B <[email protected]>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.

I am setting up a private dns hierarchy. will be using 2 dns servers
for redundancy. 1 primary, 1 secondary. everything is set up and
running smoothly, but i have 1 question..

Is it necessary to replicate the "." zone to the secondary dns server?
Should i just set up a primary . "zone"
Or do i even need the . zone on the secondary dns server?

thanks.

Bill

Without its delegations a root zone will only manage to stop your DNS server
from resolving names it is not authoritative for, it won't forward, it won't
use root hints.
If this is what you want then leave it there, otherwise delete it, like most
everyone does. Then your DNS server will resolve outside names, which cannot
do with it, or you can load a secondary of the root delegations from the
root servers.
Basically, no you don't need it.

 

[Bill B]

just to clarify,

I do need the . zone, as this a completely private network - no internet
access- this dns server is the top of the hierarchy. I dont want it to
forward or use root hints.


I want to know if i need to replicate this . zone to the other dns server
that is acting as the secondary on this same private network. I am
replicating the forward and reverse zone already, but am wondering if the
secondary server also needs to have the . zone.

and if it does, should i set it up myself or just replicate it?

Thanks


Bill

 

[Kevin D. Goodknecht Sr. [MVP]]

In

just to clarify,

I do need the . zone, as this a completely private network - no
internet access- this dns server is the top of the hierarchy. I dont
want it to forward or use root hints.


I want to know if i need to replicate this . zone to the other dns
server that is acting as the secondary on this same private network.
I am replicating the forward and reverse zone already, but am
wondering if the secondary server also needs to have the . zone.

and if it does, should i set it up myself or just replicate it?

If you don't need or want external resolution then having the root in place
might be desirable. It does not need to be replicated since it is empty you
can make it a primary or AD integrated if it is on a DC.

 

[Bill B]

Thanks a bunch
thats exactly how ist set up now, just confirming i was doing it right.

Bill