1

Windows 2003 and 2008 AD integrated DNS zones

view story
linux-howto

http://serverfault.com – We have a Windows 2003 server DC1 which is our primary DC holding all FSMO roles. It also is a DNS server for our domain domain.local which is an active directory integrated zone. We also have a Windows 2008 DC name DC2 which is a DNS server with ad integrated zone for domain.local. Both zones are set to "replication: All domain controllers in this domain (for windows 2000 compatibility)" All servers have the correct DNS entries etc. However in all dns servers dns event log there are event id 4515 indicating there are duplicate zones in separate directory partitions and only one will be us (HowTos)

taskli's picture
Submitted by taskli on 10/16/2012

Stories similar to Windows 2003 and 2008 AD integrated DNS zones

This Saturday evening we're going to be replacing our existing Windows Server 2003 domain controllers/dns servers with Windows Server 2008 R2 domain controllers/dns servers. The current forest and domain functional levels are Windows Server 2003 and I've already run adprep /forestprep and adprep /domainprep /gprep from the W2K8R2 media on the existing schema operations master.

I'm not a networking guy by all means, I'm just a developer who dabbles enough to get into trouble and I'm there. So bear with me... :)

At my office I have a Windows 2003 Domain Controller which also services DNS. On the domain I have a handful of computers and other misc. equipment/toys. For the DNS I only created a Forward Lookup Zone for my domain (mydomain.com).

I am unable to promote my newly installed Windows Server 2012 machine to a domain controller. Joining the domain as a server that is a member of the domain worked fine.

I've seen other questions and documents about doing this, but there are some things that still confuse me.

I have a Windows Server 2008R2 Active Directory and Exchange 2010 server (client access, hub transport and mailbox roles) in a primarily Linux server environment. A Linux server running BIND9 is master for all zones, including AD specific ones, with updates allowed from the Windows server (and from a separate Linux DHCP server).

I am a dev-op (a software developer who has to do IT on the side). As a website developer, I create DNS host entries on my local Windows 2003 DNS servers - there are two DNS servers in the local domain - so that I can set up IIS7 websites on my Windows 7 development box.

We have an existing Windows Server 2003 domain and several other computers are on that network (i.e., we have Windows Server 2008 member servers, other Windows Server 2003 member servers, Windows 7 and XP workstations, and even a Windows 2000 Server member server).

I'm running into a problem adding a 2008 server to our existing 2003 domain, and as I am not a Windows admin, I'm not getting the problem here. Some reading around on Technet seems to indicate that DNS devolution is the issue.

Here's the setup: DNS for the entire company is hosted on a Unix server running Bind, including the service records for the Windows domain.

I have searched high and low for a solution to this problem.

I have multiple servers running 2000, 2003, 2003 R2 and 2008 R2 using active directory and all on the same single domain.

The servers run showing the network profile as Domain which is fine and correct. However, when a windows update is installed the server changes the profile to unidentified once it has rebooted.