IT Employment

More information may be pertinent, but ....

You need to create an NS record in the parent domain pointing to the name server on the child domain. An A record in the parent domain for the name server of the child domain, a.k.a. "glue record", is also required on the name server in the parent domain.

It sounds like you are running dcpromo on the second server and hoping that it creates the child domain. Although I am aware that the option to allow the dcpromo wizard to create the DNS zones is available, I have found more success by creating the DNS zones prior to running dcpromo.

Also, delegation alone does NOT ensure redundancy. I believe you are referring to having an AD integrated zone as being redundant due to multimaster replication.

HTH,

briandesu

Sounds like you will need to point your child domain server's preferred dns entry to your root domain's dns server ip address.
1. Promote your server into the child domain.
2. On your root domain's dns server, delete the child domain's zone.
3. On your root domain's dns server, create a delegation that points to your child domain's dns server.
4. On the child domain's dns server, ensure replication has completed.
5. Once repl has completed, point the preferred dns ip address to itself
6. create the new child dns zone (should be <childdomain>.<rootdomain> example: contoso.microsoft.com
7. once it's created it should autopolulate or you can run netdiag /fix this will ensure all your necessary dns entries are in your dns zone.
8. add a conditional forwarding entry pointing to your parent zone.
9. If you have other domains in your forest, ensure that you also have a delegated zone pointing to the child domains' dns servers.

hope this helps...take care