Archived from groups: microsoft.public.win2000.dns (
More info?)
"Steve" <Steve@discussions.microsoft.com> wrote in message
news:AE87E8B4-8C90-4574-8EFE-F458230D8460@microsoft.com...
> Hi All;
>
> Got 2 Win2k DNS INTERNAL servers running (1 pri and 1 sec).
>
> 1.) On the zone transfer tab should I only be adding each other's IP
address
> or is any server OK here?
On the Primary you must EITHER:
Allow transfers to all servers
Allow transfer to the specific Secondary (add the IP address)
Allow zone transfers to those on the DNS tab (similar to previous)
One the Secondary there is no reason to add ANY servers
UNLESS you later add another secondary AND it will transfer
from that Secondary instead of the Primary (perfectly legal.)
Oh, and if you wish to be able to do nslookup "list" of the zone
from a workstation, you must also allow zone transfers to the
WORKSTATION you will use, and do this on each server which
will allow it.
Primary's never do zone transfers (except if you use
that machine as a "workstation" for listing domains
at the command line.)
AD-Integrated DNS servers never do zone transfers
between themselves (other AD-Integrated).
AD integrated may (optionally) allow them to ordinary
secondaries.
> 2.) Same for the notify tab, should it be "server in the Name server tab"
or
> "the following servers"?
If you allow zone transfers to any or all DNS servers,
you may optionally specify the server(s) for notification.
(There is no point in notifying a server which cannot
transfer our zones.)
If your refresh times (periodic zone transfer frequency)
is set LONG it is a good idea in many cases to notify
other Secondary servers.
You would want to do this judiciously if you were
notifying a Secondary that is across a WAN but notice
that notification is strictly a performance/freshness
issue.
Facebook
Twitter
Instagram