Overview of structure:
1 Server in Parent domain (rdc1.parent.com)
2 servers in Child domain (chdc1.child.parent.com & chdc2.child.parent.com)
We also have public DNS (available from the outside) that unfortunately matches our internal parent domain (parent.com). Address for internal parent.com resolve to internal IP scheme which is different that the outside scheme.
AD is 2003, DNS is on the AD servers in both parent and child domains. When the rdc1.parent.com controller is up, resolution happens as it should (or as we would expect). Requests from a child machine hit the child DC's dns, that DC then forwards it to the parent and we resolve internal addressing. As soon as that parent goes down, however, we start resolving the parent.com domain via the public internet DNS servers. To resolve this, we created, on all DNS servers in the child domain, a secondary zone and are pulling that zone from the rdc1.parent.com.
Is this the correct procedure for configuring DNS in a parent/child situation - or should it look different?