DNS configuration issue with two DC's.

No you DO NOT want an alternate in the server config
DC2 Windows Server 2003
DNS lists both DC1 and DC2

As stated in the link that brent gave KCTS give an explnation why.  It can create a looping effect.
Each server should point to itself for the primary and the secondary/alternate should be blank.



KCTS:I assume you mean PREFRRED not PRIMARY. Primary DNS servers are something different altogether.
Windows DNS servers should point to themselves as preferred DNS server. The Alternate DNS server should be blank - otherwise you can get "looping" occuring.

Its always a good idea to make at least one other DC a global catalog server as the others have said.

Also make sure that all clients have the address of a windows DNS server as their preferred DNS servert and the address of another windows DNS server as the alternate DNS server. Check both the DHCP options and the TCP/IP settings on the network card.

Make sure that the only place external DNS servers appear are on the Forwarding tab in DNS on the DNS servers themselves

Hi,
You have configured DNS on windows server 2003 so for that reason it is showing 2 DNS entries and where as windows server 2000 is an Old version of OS and windows server 2003 is a upgraded version for windows 2000 ,on which computer you have configured DNS and check both forward lookup zone as well as reverse lookup zone whether you have configured your DNS correctly ,i think DC2 windows 2003 is a Domain Controller so for that reason it is showing both DC1 windows 2000 and DC2 windows 2003 itself.

ryansoto,

KCTS does not know what he is talking about with the alternate DNS

Hi Everyone,

Both are Domain controllers. I have listed more info below. Forward and reverse lookup works with no issues.

DC1
Ipconfig setting
DNS Primary Server DC2
DNS Primary Server DC1

DC2
Ipconfig setting
DNS Primary Server DC1
DNS Secondary Server DC2

Workstations
Ipconfig settings
DNS Primary Server DC2
DNS Secondary Server DC1

DC1
Schema Master

DC2
RID master
PDC master
Infrastructure master
Domain Naming master

Both DC's are Global Catalogs

oops!

DC1 Ipconfig settings above should be:
DNS Primary Server DC2
DNS Secondary Server DC1

The only thing there that might cause an issue is the Global Catalog being on the Infrastructure Master role holder. That can cause some issues but, if you only have 2 DCs, you would want to keep it the way it is so that if one DC goes down, the other can handle the login requests. If you have more than 2 DCs, then it is best practice to not have the infrastructure master on the same server as a GC.

See
http://support.microsoft.com/kb/248047
http://support.microsoft.com/kb/223346

Other than that, your config looks good.

So should both DC's be pointing to each other? I am getting ready to add another Domain Controller DC3 and will make it the preferred DNS server. So are the settings below correct? Also note, for the moment  we use a firewall router for our DHCP IP addresses. It will also be configured to have DC3 as the preferred. (eventually I will setup the DC to run DHCP)

DC2
Preferred DC3
Alternate DC2

DC3
Preferred DC3
Alternate blank

DC1
Preferred DC3
Alternate DC2

Primary DC dont exist if the DNS is integrated in Active Directory? I have never messed with having a primary DC and a secondary DC.

Wouldn't this possibly create a little bit of a problem when a machine logs in? All the workstations are going to have a preferred DNS. As soon as that machine logs in it is registered in the DNS on the preferred DC. The other two DC's wont see that until the AD replicates to them.  I am not for sure if I am right here but just throwing it out there.

No this would not be an issue. You want each machine to try to contact its most reliable (usually via network speed) therefore an DC running AD integrated DNS should use itself primarily for internal DNS lookups and then use forwarders for extneral DNS lookups.

The clients should use the same configuration. A client in the same site as DC1 should use DC1 as the primary DNS server and the next best option for the secondary.

Understood. However, what if all the workstations are on the same site as the three DC"s? All of my workstations are pointing to one DC.

If you have 3 DC's in the one site then you could load balance them by having multiple DHCP scopes as long as they are all connected with a high speed reliable network connection it will be fine.

Hi mass2612,

Aww true I like that idea. However, my network isnt using DHCP from the servers--it will in the future though. I am trying cleanup and make better what i currently have. I didnt set this server up in the beginning.

But right now I have a VPN/Firewall router that assigns all IP addresses. It has our DC2 listed as the preferred and DC1 listed as the alternate. SO thats why i figured that all dc's and workstations should point to the preferred DC. By the way we only have about 25 users. With this configuration you still recommend the DNS servers to point to themselves?

Its been my experience that you always point the DNS servers to themselves in tcpip then in the dns forwarders tab you set to your ISP.
In your DHCP scopes is where you set multiple DNS servers so if one machine is down dns can resolved by the other dns servers listed in your scope.

I would use static settings for all servers and only have the workstations assigned automatically. That way the servers can be more easily controlled.