D
David
We are adding a Domain Controller/DNS server to a branch office that will be
persistently VPN-connected to the main office (which has one Domain
Controller/DNS server). I've set up the new server at the main office, and
all is well so far. Both are Windows 2000 servers running Active
Directory-integrated DNS; AD changes on one server can be seen on the other.
In the IP settings of the Local Area connection, I've entered each server's
own IP address for the primary DNS server, and the other DC's IP address for
the secondary DNS server. So the DNS servers point to themselves for their
primary DNS server, and each other for secondary. Sound OK? How about when
we add another branch office DC/DNS server?
Thanks for your help!
David
persistently VPN-connected to the main office (which has one Domain
Controller/DNS server). I've set up the new server at the main office, and
all is well so far. Both are Windows 2000 servers running Active
Directory-integrated DNS; AD changes on one server can be seen on the other.
In the IP settings of the Local Area connection, I've entered each server's
own IP address for the primary DNS server, and the other DC's IP address for
the secondary DNS server. So the DNS servers point to themselves for their
primary DNS server, and each other for secondary. Sound OK? How about when
we add another branch office DC/DNS server?
Thanks for your help!
David