A network with more than one primary DNS? Please HELP!!

  • Thread starter Thread starter Cheuk Man
  • Start date Start date
C

Cheuk Man

Hi all, I am new to windows networking. I am facing a DNS
problem in a network that I don't know how to resolve. The
scenario is described below:

<<Single forest and single domain with less than 100
hosts>>
DNS problem:
DC1 in acme.com - ip 192.168.1.1
pri DNS - ip 192.168.1.1
sec DNS - ip 192.168.1.2
DC2 in acme.com - ip 192.168.1.2
pri DNS - ip 192.168.1.1
sec DNS - ip 192.168.1.2
Srv1 in acme.com - ip 192.168.1.3
pri DNS - ip 192.168.1.3
sec DNS - ip 192.168.1.2

How should I approach this? Can I just manually change all
servers & DCs & clients to point to the same pri DNS and
same sec DNS? What would a similar network configuration
be like?

Could anyone give me some hints?

Warmest regards,
Cheuk Man
 
But, what exactly is the "problem"?

As to the DNS design, I'd go with something like this:

First, Srv1 does not seem to be a DC, so it can not have an AD-integrated
zone. So, unless you REALLY MUST run DNS on this server, I don't see why you
can't just remove it from the picture. 2 DNS servers should be sufficient
for hundreds of clients.

So, in my recommendation, you'd have

DC1 in acme.com - ip 192.168.1.1
pri DNS - ip 192.168.1.2
sec DNS - ip 192.168.1.1
DC2 in acme.com - ip 192.168.1.2
pri DNS - ip 192.168.1.1
sec DNS - ip 192.168.1.2

In DCHP scorpes (IF you use DHCP), you will have "pri DNS 192.168.1.1/sec
DNS 192.168.1.2" for one Scope and "pri DNS 192.168.1.2/sec DNS 192.168.1.1"
for another scope. Just alternate them so you can have something like
load-balancing.

Hope that makes sense to you.

Deji
 
Back
Top