Re: conditional forwarder required on the child domain to resolve pare
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Wed, 21 May 2008 13:14:35 -0500
That's one way but not really "required".
"study" <study@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C9FA0F89-02E9-4144-AAB9-DDE67690DA40@xxxxxxxxxxxxxxxx
The parent domain's DNS doesn't have issues resolving the child domain (I
did
create a stub zone on the parent DNS for resolving the child domain).
Again, one way, but traditionally it is done with "delegation" (Stubs are
a new feature of Win2003.)
I noticed that on the child domain's DNS, without adding a conditional
forwarder for resolving the parent domain by adding the IP of the parent
domain's DNS server, it fails to resolve the parent domain.
Is this what normally needs to be done?
Yes. The child DNS Servers must be able to find the parent (and all other
Forest zones) to work correctly and fully.
There are MANY ways (with 2003), including holding a copy (as a Secondary)
of the parent or root zone, holding a stub, conditional forwarding, holding
an AD Integrated zone copy with Forest wide replication scope, or even in
some odd cases unconditionally forwarding.
BOTTOM LINE: ALL DNS servers within your forest must be able to resolve
ALL Zone (and probably the Internet) either directly or indirectly for
things to
work correctly.
.
- Prev by Date: Re: gc doesn't show via nslookup
- Next by Date: Re: Name lookup problem, clear cache fixes?
- Previous by thread: Dynamic DNS updates 'pending' after DHCP server move
- Next by thread: Re: conditional forwarder required on the child domain to resolve
- Index(es):
Relevant Pages
|
