J
Jonathan Horne
in my windows 2000 lab environment, i have a parent
domain, and 1 child. 4 win2k servers in all, 2 for the
parent, and 2 for the child. the AD dns zone created and
replicated as normal between the 2 dns servers on the
parent domain DCs, but when i created the child, the DNS
information did not replicate across. the child was
created by adding a new domain to existing forest, and
choosing the name of my parent zone, than naming the
child zone, so that it would create child.parent.dom.
in the parent's dns snapin, i see all the typical AD
related items in the zone, as well as host records for my
2 dcs and a couple of win2k pro boxes. all seems
completly normal with the parent zone.
i manually added an AD aware dns zone of the parent
domain into the dns servers on the child DCs. they have
only the main zone, and under the main, the subdomain
zone, but none of the other normal items like _msdcs,
_sites, _tcp, _udp (on the parent, they are there), just
the name of the parent, and the name of the child. i
also have 1 win2kpro box joined to the child domain. if
i try to resolve its name (from the pro box), it
resolves, but the child domains dns server says "***
Can't find server name for address 192.168.128.102: Non-
existent domain", then answers the query with the correct
ip address for the pro box.
am i doing something wrong here? if i am, can someone
lay out the way they go about creating child domains with
replication of DNS between them?
ideally (and maybe it really doesnt work this way,so if
it doesnt, set me straight), i would like to have all the
DNS servers able to correctly resolve any host from any
domain. so in my mind, that means all dns servers should
contain the same data?
thanks for reading,
jonathan
domain, and 1 child. 4 win2k servers in all, 2 for the
parent, and 2 for the child. the AD dns zone created and
replicated as normal between the 2 dns servers on the
parent domain DCs, but when i created the child, the DNS
information did not replicate across. the child was
created by adding a new domain to existing forest, and
choosing the name of my parent zone, than naming the
child zone, so that it would create child.parent.dom.
in the parent's dns snapin, i see all the typical AD
related items in the zone, as well as host records for my
2 dcs and a couple of win2k pro boxes. all seems
completly normal with the parent zone.
i manually added an AD aware dns zone of the parent
domain into the dns servers on the child DCs. they have
only the main zone, and under the main, the subdomain
zone, but none of the other normal items like _msdcs,
_sites, _tcp, _udp (on the parent, they are there), just
the name of the parent, and the name of the child. i
also have 1 win2kpro box joined to the child domain. if
i try to resolve its name (from the pro box), it
resolves, but the child domains dns server says "***
Can't find server name for address 192.168.128.102: Non-
existent domain", then answers the query with the correct
ip address for the pro box.
am i doing something wrong here? if i am, can someone
lay out the way they go about creating child domains with
replication of DNS between them?
ideally (and maybe it really doesnt work this way,so if
it doesnt, set me straight), i would like to have all the
DNS servers able to correctly resolve any host from any
domain. so in my mind, that means all dns servers should
contain the same data?
thanks for reading,
jonathan