Re: Additional DC

* John Doe <jdoe@j23k4j76j7l9a0j0-ruei=ow835ufdklahgl.com>:
I've heard different suggestions. Some say as follows:
DC1 - primary DNS points to itself, secondary empty
DC2 - primary DNS points to DC1, secondary to itself

Not sure which configuration is better.

Not sure either. I do not really understand what purpose the
above configuration would serve, especially because DCs in an
Active Directory Domain are not really different from each other.

The idea behind the "cross over" concept is that you can reboot
one DC (while the other one is running), and not get any error
messages during boot - because there's a race condition with
Active Directory becoming active, and the DNS server becoming
active (because it depends on active directory, and vice versa).

Maybe someone with more experience on this field can shed a bit
more details into the working of such configurations.

What about WINS? I'm planning to install WINS on DC2 (the additional DC that
I'm about to add). DC1 has no WINS installed. Sounds good or do I need 2
WINS?

Using WINS in a network reduces broadcast traffic and makes
communication across WAN lines possible - it is possible to not
use WINS, but that would mean disabling NetBIOS over TCP on all
the clients. If you've already done that, a WINS server is not
necessary.

--
Read my blog at http://projectdream.org
.

Relevant Pages

  • Re: Event ID: 40960
    ... Below are the results for the ipconfig /all for both DCs (DC1 and DC2) ... Windows IP Configuration ... Ethernet adapter Local Area Connection: ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.dns)
  • Re: Replication problem with wrong dns name in active directory
    ... from a command prompt on DC1 ... Run diagnostics against your Active Directory domain. ... netdiag and repadmin in verbose mode. ... name for the destination domain controller is not registered on the ...
    (microsoft.public.windows.server.active_directory)
  • Re: Win2000 Server w/o AD
    ... (A good reference if that's the way you want to go: Configuring Windows 2000 ... Without Active Directory, by Syngress Media: ... If you require a domain configuration, then you'll need to configure Active ... This applies to both Windows 2000 & Windows Server 2003. ...
    (microsoft.public.win2000.active_directory)
  • Re: netlogon to domain for clients at branch office w/o DC
    ... This configuration should be simple over a T1/VPN. ... built-in filters or firewalls. ... the client machines all have DC as theri primary DNS. ... >> Doug Sherman ...
    (microsoft.public.win2000.networking)
  • Re: DNS server nslookup failure
    ... Windows IP Configuration ... Ethernet adapter Broadcom NetXtreme Gigabit Ethernet ... >> automatically created when I set up Active Directory. ...
    (microsoft.public.windows.server.dns)