DNS Config.,.

  • Thread starter Thread starter Dragon
  • Start date Start date
D

Dragon

Hi,

I have two Win2K DCs with AD integrated DNS. I wanted to know which IPs
should I configure on each server as its DNS server.Here is how I have it
configured right now:

DC1
IP: 192.168.1.1
DNS1: 192.168.1.1
DNS2: 192.168.1.2

DC2
IP: 192.168.1.2
DNS1: 192.168.1.2
DNS2: 192.168.1.1

Thank you.
 
In
Dragon said:
Hi,

I have two Win2K DCs with AD integrated DNS. I wanted to know which
IPs should I configure on each server as its DNS server.Here is how I
have it configured right now:

DC1
IP: 192.168.1.1
DNS1: 192.168.1.1
DNS2: 192.168.1.2

DC2
IP: 192.168.1.2
DNS1: 192.168.1.2
DNS2: 192.168.1.1

Thank you.
Click to expand...


Recommended suggestion (provided they're on the same subnet and not across a
WAN link):

DC1
IP: 192.168.1.1
DNS1: 192.168.1.2
DNS2: 192.168.1.1

DC2
IP: 192.168.1.2
DNS1: 192.168.1.1
DNS2: 192.168.1.2


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Ace,

Can you explain why MS is recomending this configuraiton? I remember we had
Island problem in W2k but they fixed it in SP4.

Note: For the first DC installtion you have to point the DNS server to
itself !!

Santhosh


"Ace Fekay [MVP]"
 
In
Santhosh Sivarajan said:
Ace,

Can you explain why MS is recomending this configuraiton? I remember
we had Island problem in W2k but they fixed it in SP4.

Note: For the first DC installtion you have to point the DNS server to
itself !!
Click to expand...

It eliminates any possiblitly of the Island issue (even though SP2 fixed
it). It also eliminates any possibility of 5781 errors where the zone is not
available due to the AD database not yet initialized. This occurs
*occasionaly* mostly due to if the server is overloaded or not. It's more or
less now "Best Practice".


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Hi,
The best configuration is to configure only one DNS.
The first DNS is always the own IP-Adress.
It's the idea of AD (the DNS-Replication in AD)

Is in your configuration the DNS-Server's DNS-databese
corrupt (for example), he contacts the 2nd DNS. He will
never repair his own database and he will never look in
his own database, because he has the 2nd DNS.

I hope, it helps you. (my english isn't the best :-)
li
 
In
lisa said:
Hi,
The best configuration is to configure only one DNS.
The first DNS is always the own IP-Adress.
Click to expand...

Actually to touch base on this statement, this is not always the best
configuration. If there are more than one DC/DNS on a subnet, it's
recommended (and consensus among the engineers) to point to the partner DNS
as the first entry and itself as the second entry. This eliminates a couple
errors and possible problems.

But in most cases, if the only one on a subnet, and there is another in
anohter subnet (remote location), point to itself first, then the other one
in the remote location as the second entry.

If the only DC/DNS, then only point to itself.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
Dragon said:
Thank you Ace and everyone for your help.
Click to expand...

You're welcome.
:-)

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top