Re: Any reason for this DNS setup?

Kevin, thank you so much for your help and quick responses. Your help is
much appreciated.

BTW, we are going to retire all DCs. We are going to use new hardwares. I
plan to intall Windows 2003 on one new server and promote and transfer FSMO
roles on root and child domain; then introduce more DCs for load balance and
fault tolence for root domain and child domain for some time. That means
that Windows 2000 DCs will co-exist with Windows 2003 DCs.

>After you upgrade the parent domain and before you upgrade the Win2k child
> DCs, you should delete the secondary _msdcs.us.local zone

In my situation above, should I delete the secondary first?

BTW, what are right steps or suggestions for moving to windows 2003 envir.
if we are going to use different new servers?

Thank you!

Peter




"Kevin D. Goodknecht Sr. [MVP]" wrote:

> Peter <Peter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> > Hi all,
> >
> > I just moved to this company. I have a little confusion about their
> > DNS setup. We have Windows 2000 active directory. We have two Root
> > domain controllers and root domain is us.local and child domain is
> > child.us.local and three child domain controllers. On the root
> > domain, there are two active directory integrated forward zone:
> > us.local and _msdcs.us.local(dc, domains, gc, pdc inside this zone).
> > In the child domain, there is secondary zone created for
> > _msdcs.us.local.
>
> The reason they have created this zone as a secondary is that the records in
> the _msdcs.us.local must be available throughout the forest. Win2k3 does
> this by default by creating this zone replicated to all DNS servers in the
> forest.
>
> >
> > I do not know why they have created secondary zone for
> > _msdcs.us.local? (root domain recources) They do not use active
> > directory integrated zone and use secondary zone? Any clue?
>
> Because Win2k does not have forest wide replicated zones, they have mimicked
> Win2k3 behavior by creating this as a secondary zone.
> Under Win2k3, this zone is created and is set to replicate to all DNS
> servers in the forest. Since the partition this zone is in Win2k does not
> get zones replicated in this partition.
>
> >
> > If I have root domain us.local and child domain internal.us.local,
> > What other forward lookup zones should show up on root and child
> > domain besides us.local and child.us.local?
> >
> > BTW, we are going to move Windows 2003 environment and any issue with
> > this DNS setup?
>
> After you upgrade the parent domain and before you upgrade the Win2k child
> DCs, you should delete the secondary _msdcs.us.local zone. Do this because
> when you upgrade the child DCs it will load the zone from the forest wide
> replication partition.
>
> 817470 - HOW TO: Reconfigure an _msdcs Subdomain to a Forest-wide DNS
> Application Directory Partition When You Upgrade from Windows 2000 to
> Windows Server 2003
> http://support.microsoft.com/default.aspx?scid=kb;en-us;817470&sd=RMVP
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> https://secure.lsaol.com/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>
>
.

Relevant Pages

  • Re: Any reason for this DNS setup?
    ... we are going to retire all DCs. ... > promote and transfer FSMO roles on root and child domain; ... a delegation is made under the parent zone for the child zone to ... the replication scope settings on the 2003 DNS server with the AD Integrated ...
    (microsoft.public.windows.server.dns)
  • Re: gc doesnt show via nslookup
    ... results but when I do _msdcs.pri.ad.domain.com on the child domain, ... as a separate zone that replicates Forest Wide so it is ... available in all Domains and so all DCs can make their Netlogon ... registrations in the zone. ...
    (microsoft.public.windows.server.dns)
  • Re: DNS resolving issues
    ... When you configure a child domain you either create a sub domain or delegate ... to do this would be to create a secondary zone that pulls the AD-Integrated ... the zone transfers tab is only used for DNS servers ...
    (microsoft.public.win2000.dns)
  • Re: Any reason for this DNS setup?
    ... we are going to retire all DCs. ... > promote and transfer FSMO roles on root and child domain; ... where the master _msdcs.us.local zone is, ... If you are going to use new servers, you will just add them as replica DCs, ...
    (microsoft.public.windows.server.dns)
  • Re: AD Integrated DNS - Misconfigured Replication
    ... The child domain does not appear to be a sub-domain of the parent domain. ... DNS is child_domain.parent_domain.com. ... The DNS zone named child_domain.parent_domain.com was created on the ... created on the child_domain DCs with the replication scheme "All DCs ...
    (microsoft.public.windows.server.dns)
Loading