SOA DNS Missing in Child Domain - DCDiag /v /test:DNS

When running  DCDiag /v /test:DNS I receive the following warning
"The A record for this DC was found
The SOA record for the Active Directory zone was not found
Warning: The Active Directory zone on this DC/DNS server was not found (probably a misconfiguration)
Root zone on this DC/DNS server was not found"

The DNS test passes but I am concerned about this message.  We currently have a 5 Root dc's that are all DNS servers strategically placed geographically across the company.  We have 5 child domains that have no DNS servers except the new child domain we are migrating to.  There are four DCs in the new child domain and we have made the decision to make those AD Integrated, receiving all zones from the root DC's of the forest. (which was done first before making the new child domain controllers DNS servers).

If I logon to a new child domain DNS server and click on the root domain (xyz.int) I see the child domain DNS server as the SOA record.  If I click down to the new child domain dns (newchild.xyz.int) there is no SOA record for that DC.  This seems to be what the dcdiag is complaining about.  

Any ideas if I can ingore this or do I truly have a misconfiguration as the warning states.

                 
cweldoncdAsked:
Who is Participating?
 
Darius GhassemCommented:
You need to configure this it will overall cause less issues and give you a manageable domain.
0
 
Darius GhassemCommented:
0
 
cweldoncdAuthor Commented:
No, I guess I was looking at this newchild.xyz.int as a zone but it really isnt.  It is just a folder under the xyz.int zone.  Therefore, it would really have a SOA in the newchild folder.  The obvious solution is to create a zone for the newchild.xyz.int but you would have to delete the folder underneath the xyz.int first wouldnt you?  I really don't want to do that!
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Darius GhassemCommented:
When you have child domains you want to manage seperately
0
 
cweldoncdAuthor Commented:
So what would be the steps to making the child domain its own zone in AD-Integrated DNS?  I have multiple domain structure (1 forest) and we are about to begin a collapse of all the computers into the 1 single child domain.  This could be risky since I already have 25 servers in the new domain.
0
 
Darius GhassemCommented:
What you want to do is create child.domain.com zone this will then replicate over to the other DNS servers since you are running AD integrated zones. The zone will replicate throughout your DNS namespace (tree)
0
 
cweldoncdAuthor Commented:
Would there be two places that the child.domain.com "contents" would exist?  I guess I am not understading what the end state of DNS would look like and how all of the _msdcs, sites, gc, etc folders would react and how my domain controlles respond to this change.  Would I need to do anything to my domain controllers such as start and stop netlogon, reboot.  A lot to think about here or am I making it to difficult.
0
 
Darius GhassemCommented:
When you create the child.domain.com zone you would then restart the netlogon service or dcdiag /fix to create the records under the child.domain.com zone which will have all folder listed under the zone.
0
 
cweldoncdAuthor Commented:
Would you consider this a critical thing to do for my child domain.  Do you forsee Active Directory, GPO's, other applications not working properly if I do not configure this?
0
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.

All Courses

From novice to tech pro — start learning today.