Stub zones do auto upate the NS record
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/sag_DNS_und_StubZones.asp
When the administrator of the authoritative DNS server for
example.com updates the stub zone, it queries the stub zone's master
servers to obtain the authoritative DNS server resource records for
widgets.example.com. Consequently, the DNS server authoritative for
the parent zone will learn about the new DNS servers authoritative
for the widgets.example.com child zone and be able to perform
recursion to all of the child zone's authoritative DNS servers.
The Stub Zone master will have to be specified but after that the Stub Zone
auto udpates for all NS servers.
Regards;
James R. Day
Active Directory Core Team
Office of the Chief Information Officer
National Park Service
(202) 354-1464 (direct)
(202) 371-1549 (fax)
[EMAIL PROTECTED]
|---------+---------------------------------->
| | [EMAIL PROTECTED]|
| | com |
| | Sent by: |
| | [EMAIL PROTECTED]|
| | tivedir.org |
| | |
| | |
| | 03/10/2005 02:46 PM EST|
| | Please respond to |
| | ActiveDir |
|---------+---------------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [email protected]
|
| cc: (bcc: James Day/Contractor/NPS)
|
| Subject: RE: [ActiveDir] [Activator] DNS - Stub Zones -vs- Referral
Zones |
>------------------------------------------------------------------------------------------------------------------------------|
No, I was under the impression that a stub zone dynamically updates NS/SOA.
Guess not. My bad.
We were just looking for a way to not have to manually update NS for the
sub zones.
Thanks,
J
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, March 10, 2005 2:30 PM
To: [email protected]
Subject: RE: [ActiveDir] DNS - Stub Zones -vs- Referral Zones
Why do you think it is necessary to kill the sub zones? Because you donât
want to worry about NS records changes? Well, you will have to worry about
that in stub configurations, too. If your NS/SOA changes, you will still
have to update the stub zone accordingly.
Did I misunderstand your question?
Deji
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, March 10, 2005 10:14 AM
To: [email protected]
Subject: [ActiveDir] DNS - Stub Zones -vs- Referral Zones
Hey everyone, DNS question:
On our Forest Root DNS servers, in the root DNS forward lookup zone, there
are sub zones (I think they are Referral Zones) for each sub-domain.
In these sub-zones there are NS records for the DNS servers in each sub
domain.
For example:
Root.company.com
_msdcs
_site
_tcp
_udp
Subdomain1 (contains NS record: dc.subdomain1.rootdomain.com)
Subdomain2 (contains NS record: dc.subdomain2.rootdomain.com)
Would we be better off killing the sub zones and going with stub zones, if
possible? Basically, we want to avoid manually changing the NS records. I
think stubs are dynamically updated, could be wrong.
Thanks,
Jbl
This e-mail, and any attachment, is intended only for the person or entity
to which it is addressed and may contain confidential and/or privileged
material. Any review, re-transmission, copying, dissemination or other use
of this information by persons or entities other than the intended
recipient is prohibited. If you received this in error, please contact the
sender and delete the material from any computer. The contents of this
message may contain personal views which are not the views of Discovery
Communications, Inc. (DCI).
This e-mail, and any attachment, is intended only for the person or entity
to which it is addressed and may contain confidential and/or privileged
material. Any review, re-transmission, copying, dissemination or other use
of this information by persons or entities other than the intended
recipient is prohibited. If you received this in error, please contact the
sender and delete the material from any computer. The contents of this
message may contain personal views which are not the views of Discovery
Communications, Inc. (DCI).
