site to site, Parent domain/child domain DNS

[Tom Rodgers]

Win2k server was recently set up to create a new forest.
Parent domain was set up with DNS and AD. Child domain
was added in remote office, also with DNS and AD. In
parent, DNS has forward zone company.com with DC as SOA
for zone. When child was set up as child.company.com, the
forward zone company.com was also created with DC of
child.company.com as SOA. I believe this is incorrect and
child's zone should be Child.company.com and child DC can
be SOA for that zone.

Currently, when I monitor replication for Parent DC it
appears to be going through relatively regularly. But if
I choose to monitor child DC replication has failed for

1700 times (it is set for every 15 min for past 2+

weeks). Failure is due to DNS problem according to message

All help is greatly appreciated

Thanks,
Tom

 

[Guest]

-----Original Message-----
Win2k server was recently set up to create a new forest.
Parent domain was set up with DNS and AD. Child domain
was added in remote office, also with DNS and AD. In
parent, DNS has forward zone company.com with DC as SOA
for zone. When child was set up as child.company.com, the
forward zone company.com was also created with DC of
child.company.com as SOA. I believe this is incorrect and
child's zone should be Child.company.com and child DC can
be SOA for that zone.

Currently, when I monitor replication for Parent DC it
appears to be going through relatively regularly. But if
I choose to monitor child DC replication has failed for
weeks). Failure is due to DNS problem according to message

All help is greatly appreciated

Thanks,
Tom
.

 

[Michael Johnston [MSFT]]

In the parent domain, make sure that there is a delegation for the child domain that points to the child DC as the NS server for that zone. Without this the parent
has no way of finding the child. Second, you need to tell the child how to get to the parent. There are two ways to accomplish this. Depending on your
environment, you need to choose the right option for you. The first option, would be to configured forwarders on the child DNS server to forward requests to the
parent. The second option would be to configure a secondary on the child DNS server for the parent domain. With a zone transfer, the child would then be
able to resolve parent domain resources. You will need to make sure that the parent is configured to allow zone transfers to the child. By default it's not.

Thank you,
Mike Johnston
Microsoft Network Support


--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.

 

[Tom Rodgers]

Thanks Mike. I was able to create the child domain zone
on the remote server as AD zone and then set up secondary
on local server for child zone and transfer from master.
Then did same for parent domain removing the ADzone from
child DNS and creating new secondary instead and doing
transfer from master.

Now both DNS servers have the same info and are SOA for
their own zones. And, when I synched the replication it
was successful so both servers should now have same AD
info.

Also having some Exchange issues but that's for another
group. maybe DNS resolution will solve some of those
problems too ;-)

Thanks again,
Tom

-----Original Message-----
In the parent domain, make sure that there is a

delegation for the child domain that points to the child
DC as the NS server for that zone. Without this the
parent

has no way of finding the child. Second, you need to

tell the child how to get to the parent. There are two
ways to accomplish this. Depending on your

environment, you need to choose the right option for

you. The first option, would be to configured forwarders
on the child DNS server to forward requests to the

parent. The second option would be to configure a

secondary on the child DNS server for the parent domain.
With a zone transfer, the child would then be

able to resolve parent domain resources. You will need

to make sure that the parent is configured to allow zone
transfers to the child. By default it's not.

Thank you,
Mike Johnston
Microsoft Network Support

confers no rights. Use of included script samples are
subject to the terms specified at

http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all

responses to this message are best directed to the
newsgroup/thread from which they originated.