DNS was not setup properly, need to make a choice from 2 options, advice needed

[TwistedHelixis]

Been working through error logs and best practice analyzer at a few school. None of them were setup correctly but all are working. Basically what I have found is the _msdcs was not created properly by whoever installed server 2003 and it must have been that way ever since.

 

To fix the issue I have been told to follow some simple step by step instruction but they give me a choice at the start and I want to make sure I follow the correct choice.

 

 

• Case 1: The _msdcs.ForestName zone is a subdomain of your Active Directory-integrated forest root DNS zone, and the secondary _msdcs.ForestName zones are stored in your child domains (if child domains are present).
  

Case 2: The _msdcs.ForestName is a subdomain of your Active Directory-integrated forest root DNS zone.

 

looking at my screen capture which case do I follow 1 or 2? I recon it is 2 but would like someone with better DNS skills to advice.

 

If you need any more info please ask.

[TwistedHelixis]

So Basically I need to know from the image in my first post, is the _msdcs -

 

this zone is a subdomain of your Active Directory-integrated forest root DNS zone, and the secondary _msdcs.ForestName zones are stored in your child domains

 

or is it is a subdomain of your Active Directory-integrated forest root DNS zone.

 

Thanks

[Michael]

Personally if it works I'd leave well alone. You'll more than likely need to break DNS first before doing it what you consider the correct way.

[TwistedHelixis]

This is the MS KB I have to follow - https://support.microsoft.com/en-us/kb/817470

 

If it is case 2 I would need to do the following,

- Configure the primary DNS server setting in the network connections of all domain controllers in your forest with the IP address of a single root domain controller.

- Create the _msdcs zone for the Active Directory forest name, and then store the _msdcs.ForestName zone in the DNS forest-wide application directory partition.

- Force replication.

- Delete the old _msdcs subdomain.

 

This was written by someone who has already followed case 2

Manually create the _msdcs.ForestFQDN. right-clicked the Forward Lookup Zones/New Zone.../Next/Select "Primary zone" radio button and the "Store the zone in Active Directory" check box (these are defaults)/Next/for replication scope I selected "To all DNS servers running on domain controllers in this domain" (I have a simple single forest, single domain config)/Next/Zone Name: _msdcs.ForectFQDN

[nathan]

If its working well, then i would also leave it alone. What have you to gain?

[ADMaster]

I did the shortened steps of case 2 a while back.