disappearing secondary zones

[Keith W]

We have 2 forward lookup zones on our master DNS server:
- domain.com
- sub.domain.com
Both zones are Active-directory integrated, and both support zone
transfers to servers listed in the name servers tab.

We have 2 other DNS servers, both members of sub.domain.com. Both are
listed in the name servers tab of the DNS zones on our master DNS
server. We are trying to create secondary zones to each of the zones
on the master DNS server. We can create both domain.com and
sub.domain.com secondary forward lookup zones, and both will transfer
from the master, but after a few days, the sub.domain.com secondary
zone disappears from both of these secondary DNS servers, leaving only
the domain.com zone. The master DNS server is not affected and
retains both forward lookup zones.

Is this normal, or have we misconfigured DNS for the sub.domain.com
zone on the master? If so, how can this be set up correctly?

 

[Keith W]

After reading what I just posted, I now think we should be setting up
sub.domain.com as a primary/AD-integrated forward lookup zone on one
of the sub.domain.com DNS servers, and creating a secondary zone to
sub.domain.com on the "master" domain.com DNS server. Does this sound
right?

 

[Jorge_de_Almeida_Pinto]

We have 2 forward lookup zones on our master DNS server:
- domain.com
- sub.domain.com
Both zones are Active-directory integrated, and both support
zone
transfers to servers listed in the name servers tab.

We have 2 other DNS servers, both members of sub.domain.com.
Both are
listed in the name servers tab of the DNS zones on our master
DNS
server. We are trying to create secondary zones to each of the
zones
on the master DNS server. We can create both domain.com and
sub.domain.com secondary forward lookup zones, and both will
transfer
from the master, but after a few days, the sub.domain.com
secondary
zone disappears from both of these secondary DNS servers,
leaving only
the domain.com zone. The master DNS server is not affected
and
retains both forward lookup zones.

Is this normal, or have we misconfigured DNS for the
sub.domain.com
zone on the master? If so, how can this be set up correctly?

We have 2 forward lookup zones on our master DNS server:
- domain.com
- sub.domain.com
Both zones are Active-directory integrated, and both support zone
transfers to servers listed in the name servers tab.

We have 2 other DNS servers, both members of sub.domain.com. Both are

Leave Master DNS servers configuration as is.
Create secondary DNS zones on the 2 DNS servers which are members of
sub.domain.com and point to the master DNS server IP to transfer the
zone from

Cheers,

 

[Ace Fekay [MVP]]

After reading what I just posted, I now think we should be setting up
sub.domain.com as a primary/AD-integrated forward lookup zone on one
of the sub.domain.com DNS servers, and creating a secondary zone to
sub.domain.com on the "master" domain.com DNS server. Does this sound
right?

You could, and it may possibly be a better "best practice" solution, is to
use delegation. Since you want the admins in sub.domain.oom to administer
their own data, at the parent zone in domain.com's DNS server, create a new
delegated zone called 'sub'. Provide the IP and name of the DNS servers in
sub.domain.com. In sub.domain.com, configure forwarding back to the parent
domain.com's DNS server(s). Configure forwarding on the domain.com's DNS
servers to your ISP. This should take care of a clean resolving
infrastructure.

255248 - HOW TO Create a Child Domain in Active Directory and Delegate the
DNS Namespace to the Child Domain (Forwarding is optional, but recommended):
http://support.microsoft.com/?id=255248

Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Infinite Diversities in Infinite Combinations.
=================================