Re: Secondary zone disappears after DNS restart
- From: "Ace Fekay [MVP]" <PleaseSubstituteMyActualFirstName&LastNameHere@xxxxxxxxxxx>
- Date: Tue, 27 Sep 2005 12:48:52 -0400
In news:2B153C0B-B911-4613-8BFE-2D2E8954D2BB@xxxxxxxxxxxxx,
Alexis <alexis75@xxxxxxxxxxxxxxxxxxxxxxx> made this post, which I then
commented about below:
> Thanks
> Have tried adding a forwarder back to parent DNS, still no joy.
> Should the ADI DNS zone logics.corp in logics.corp have a delegation
> for uk with uk DNS servers as Name Servers?
Yes
>
> Why is there a delegation for uk configured in the ADI logics.corp
> zone on the DNS server in logics.corp?
Maybe someone wanted the folks down at the "uk" domain to take care of their
own zone. That is the usual reason for delegations. Just as the definition
implies, it was "delegated" the task to take care of that zone to someone
else, er, some other DNS server instead of the parent servers.
>
> Could secondary zones be used? Create a secondary zone for
> uk.logics.corp on a DNS server in logics.corp and a secondary zone
> for logics.corp on a DNS server in uk.logics.corp?
Why? Let the delegation do the work. I believe an understanding of exactly
what delegation means is in order. In a scenario where a zone is delegated,
a client in the parent zone that needs something in the child zone resolved,
will send a query for that name to their own DNS server in the parent zone,
since that client is presumably ONLY using that DNS server in it's IP
properties (best practice and the proper way to do it.) Their server says "I
don't have that data, but I know who does." And the parent DNS server will
send the query to the nameservers defined in the delegation. Those
nameservers return the answer, the parent server caches it, and returns the
answer to the client.
When a client in the child zone needs to resolve any data in the parent
zone, it will send that data to it's own DNS server in their child domain,
since that client is presumably ONLY using that DNS server in it's IP
properties (best practice and the proper way to do it.) That server says, "I
do not have that data, but I have a forwarder configured to this other DNS
server, so let me send that data to that server. Of course the forwarder is
the DNS server hosting the parent zone. That server will resolve it, send it
to the child DNS server, it then caches it and sends the response to the
client.
If you have multiple child zones, same deal.
Got it?
So there is no need for any secondaries or any other mis-configurations, to
confuse, complicate or effectively render useless this functionality.
I hope that makes sense?
:-)
Ace
.
- Follow-Ups:
- Re: Secondary zone disappears after DNS restart
- From: Alexis
- Re: Secondary zone disappears after DNS restart
- References:
- Re: Secondary zone disappears after DNS restart
- From: Ace Fekay [MVP]
- Re: Secondary zone disappears after DNS restart
- From: Alexis
- Re: Secondary zone disappears after DNS restart
- From: Alexis
- Re: Secondary zone disappears after DNS restart
- Prev by Date: Re: Can't view Computers in a different scope
- Next by Date: Re: Error 7063
- Previous by thread: Re: Secondary zone disappears after DNS restart
- Next by thread: Re: Secondary zone disappears after DNS restart
- Index(es):
Relevant Pages
|