DNS Delegation on about to be decommissioned W2k3 DC

Hello

I have a Windows 2003 native domain with 2008 R2 PDC and Secondary DCs and a 2003 SP2 DC that is about to be decommissioned. All FSMO roles are on the PDC (my boss's decision) and all DCs are Global Catalogs.

When I DCDIAG the report says that:

           DNS delegation for the domain  _msdcs.domain.local. is operational on IP 192.168.x.xx

And:
               TEST: Delegations (Del)
                  Delegation information for the zone: domain.local.
                     Delegated domain name: _msdcs.domain.local.
                        DNS server: old_dc.domain.local. IP:192.168.x.xx [Valid]

where 192.168.x.xx is the old 2003 DC. 2003 DC was an SBS server and used to be the primary (only) DC and used to run Exchange 2003 (now uninstalled).

My questions:
* What is the DNS Delegation for (we have no child domains)?
* Do I need to take any action regarding the DNS delegation before I DCPROMO it to make it just a member server?
* If so what do I need to do?

Help much appreciated.
dejectedAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DrDave242Commented:
The delegation is for the _msdcs.domain.local zone, which is effectively a child domain. (It may sometimes appear as a folder named _msdcs beneath the domain.local zone rather than a separate zone.)

In the DNS console, there should be a gray folder named _msdcs inside your domain.local zone. This is the delegation record, and it should contain name server (NS) records for each DC/DNS server that hosts a copy of the zone (every DC/DNS server in the forest by default, I believe).

Check all DCs which are also DNS servers and verify that at least one of them has an _msdcs.domain.local forward lookup zone. (It's an AD-integrated zone by default, so they should all have a copy of it unless you've changed that.) Then check the delegation record and make sure the NS records match the DCs which have a copy of the zone. If you find a discrepancy, you can only make changes by right-clicking the delegation record and selecting Properties - you can't directly modify the NS records in the delegation.

You shouldn't have to change anything if the NS records in the delegation are correct; it should be handled during the demotion, but you may want to go back and check after the server is demoted to make sure its NS record was removed from the delegation.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.