DNS seems incorrect after promoting 2008 R2 Server and demoted 2003 server as domain controllers

Posted on 2014-12-10
Last Modified: 2015-02-07
After transferring the FSMO roles to our 2008 R2 server and making it the new PDC. I was unable to get the 2003 server to graciously demote as DC, I then used the dcpromo /forceremoval, since then we are unable to reconnect the 2003 server to the domain, All the workstations can no longer connect to Exchange (also hosted on the PDC at this point), when running a nltest /dclist:domain command the domain cannot be found.  I have attached a copy of the dcdiag, any help would be appreciated.
Question by:Danbman
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
LVL 10

Expert Comment

by:Walter Padrón
ID: 40492527
You must setup the DNS role on your DC, seems is not working
"Name resolution for the name isatap timed out after none of the configured DNS servers responded."

Author Comment

ID: 40492606
DNS role is installed on DC, Best practices analyzer comes back with no errors or warnings.
LVL 10

Expert Comment

by:Walter Padrón
ID: 40492618
Check firewall rules, open DNS console and check you see your dns zones. dcdiag doesn't found any DNS servers.
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!


Author Comment

ID: 40492624
Not sure if this will help, but here is the BPA log for AD DS
LVL 10

Expert Comment

by:Walter Padrón
ID: 40492643
The BPS logs are in xml format, is difficult to red but some messages can be extracted.
"<Message>Could not find a forest identified by: 'crossroads.local'.</Message>"
this points to a DNS issue also.

Author Comment

ID: 40492688
Disabled local firewall as well as created a rule in external firewall to allow all internal traffic (just in case). Opened DNS console and am able to see the forest for the domain just fine. When trying to connect the 2003 server to the domain it states

DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain crossroads.local:

The query was for the SRV record for _ldap._tcp.dc._msdcs.crossroads.local

The following domain controllers were identified by the query:


Common causes of this error include:

- Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses.

- Domain controllers registered in DNS are not connected to the network or are not running.

For information about correcting this problem, click Help.
LVL 10

Expert Comment

by:Walter Padrón
ID: 40493850
How many domain controllers do you have now?

You must check the DNS zone for staled or wrong records pointing to non-existing DCs, do the same in your zone for NS records.

Accepted Solution

Danbman earned 0 total points
ID: 40494675
It looks like I have cleared the largest hurdle.  Turns out the issue had something to do with netlogon and sysvol shares not replicating correctly. I was able to rebuild them and now computers are able to join the networks again as well as exchange seems to be functioning again.  I would like to thank you for your help regardless Walter.

Author Closing Comment

ID: 40595418

Featured Post

Free NetCrunch network monitor licenses!

Only on Experts-Exchange: Sign-up for a free-trial and we'll send you your permanent license!

Here is what you get: 30 Nodes | Unlimited Sensors | No Time Restrictions | Absolutely FREE!

Act now. This offer ends July 14, 2017.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article shows the method of using the Resultant Set of Policy Tool to locate Group Policy that applies a particular setting.
Auditing domain password hashes is a commonly overlooked but critical requirement to ensuring secure passwords practices are followed. Methods exist to extract hashes directly for a live domain however this article describes a process to extract u…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

717 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question