So, if we want centralized management (would be nice), just setup
a master server with each seperate domain as a forward and
reverse zone, and setup all the the other servers as slaves to
that master?
Why need so many slaves at all?
You can either just do away with them (point your schools to your
DNS server on the WAN) or have them resolve through to your
Masters.
I'm assuming that this would only be if we are not forwarding on
the master? We don't want to forward to a forwarder, do we?
The concepts of masters are unrelated to forwarding. They're
unrelated to being authoritative as well, though that's not always
as obvious.
DNS is a recursive system. Just about everything needs to forward
its requests to something else, unless you have a very, very small
DNS universe. Using forwarders just defines where you send your
requests. If you've got forwarder's defined then all the requests
that the current DNS server isn't authoratative for, or aren't
currently cached, will get sent to the forwarders for further
resolution.
I guess I'm taking DNS & Bind too literally: 4th Edition, page 267:
"Avoid chaining your forwarders. Don't configure name server A to
forward to server B, and server B to forward to server C..."
I'm only talking about our one, internal domain, here, so it still
sounds to me like we shouldn't be forwarding from any server inside
our domain to another, but set them up as master/slaves.
Again, I'm sure I'm not getting it, but I'm just trying to clarify.
Thanks.
Bret
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
