DNS configuration


J

JJ

Hello

I have 2 servers acting as active directory domain controllers.

UKDC1 was installed first as the first domain controller in the forest -
ourdomain.local
UKDC2 was installed as a domain controller in the same domain -
ourdomain.local

Both servers have DNS installed.

UKDC2's DNS was automatically set up when I ran DCPromo and the
_msdcs.ourdomain.local and ourdomain.local zones exist and are the same as
UKDC1's

My question is regarding correct TCP/IP settings in the network adapter
properties

Currently both servers have 1 dns entry which points to it's own IP

eg

UKDC1
IP 192.168.1.1
SM 255.255.255.0
GW 192.168.1.100
DNS 192.168.1.1

UKDC2
IP 192.168.1.2
SM 255.255.255.0
GW 192.168.1.100
DNS 192.168.1.2

Then each server has the other server's IP set in the Forwarders tab in DNS.
Everything seems to work OK, but I feel this is inefficient and not best
practice.

Could anyone tell me what is best practice please, and also, should my
domain clients have both DNS entries in their network adapter tcpip
properties?

Thank-you
 
Ad

Advertisements

G

Guest

JJ,

Best practice with Directory Integrated DNS is to point each DC to itself
first and then to another DC (preferrably the one that is designated as the
DNS server for your environment). Hence in your case, you would point UKDC1
first to itself (DNS 1) and then to UKDNS2 (DNS 2). All the other PCs in
your environment should point to these two DNS servers for name resolution.
Also, IP forwarders are only for DNS servers that are NOT in your domain!
So, take the servers out of your IP Forwarders.

-Allen Firouz
 
Ad

Advertisements

J

Jorge_de_Almeida_Pinto

Hello

I have 2 servers acting as active directory domain
controllers.

UKDC1 was installed first as the first domain controller in
the forest -
ourdomain.local
UKDC2 was installed as a domain controller in the same domain
-
ourdomain.local

Both servers have DNS installed.

UKDC2's DNS was automatically set up when I ran DCPromo and
the
_msdcs.ourdomain.local and ourdomain.local zones exist and are
the same as
UKDC1's

My question is regarding correct TCP/IP settings in the
network adapter
properties

Currently both servers have 1 dns entry which points to it's
own IP

eg

UKDC1
IP 192.168.1.1
SM 255.255.255.0
GW 192.168.1.100
DNS 192.168.1.1

UKDC2
IP 192.168.1.2
SM 255.255.255.0
GW 192.168.1.100
DNS 192.168.1.2

Then each server has the other server's IP set in the
Forwarders tab in DNS.
Everything seems to work OK, but I feel this is inefficient
and not best
practice.

Could anyone tell me what is best practice please, and also,
should my
domain clients have both DNS entries in their network adapter
tcpip
properties?

Thank-you

If the DCs are W2K3:
Use as preferred DNS: itself
Use as alternate DNS: another DNS server

If the DCs are W2K:
see: http://support.microsoft.com/?id=275278

Remove the forwarders where the DCs/DNS servers point to each.
Forwarders are only used when pointing to other DNS servers that know
more or other DNS information (zones)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top