Re: DNS Zone merge

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Ace Fekay [MVP] (PleaseSubstituteMyActualFirstName&LastNameHere_at_hotmail.com)
Date: 02/11/04


Date: Tue, 10 Feb 2004 21:57:05 -0500

In news:e70e01c3f047$292b8c90$a601280a@phx.gbl,
anonymous@discussions.microsoft.com <anonymous@discussions.microsoft.com>
posted their thoughts, then I offered mine
> I understand how to migrate over the DNS zones. The
> problem is that in the existing DNS server the zones are
> divided up into multiple zones. For example 2k.test.com
> and child.2k.test.com. For what ever reason they made
> the two zones seperate. I would prefer it be be one zone
> on a windows 2000 domain controller. The first is an
> empty root 2k domain and the child is our production 2k
> domain. So when I make them secondary zones on the 2k
> servers prior to changing to primary I have two zones
> that migrated over. Only way I can see to get one zone
> is start over and rebuilt dns with netdiag /fix. This
> seems fine for the SRV records just a little concerned
> that some of the dynamic dns records did not repopulate
> evern after forcing ipconfig /registerdns.
>
>
>
>
>> -----Original Message-----
>> 1) Install DNS server(s) on your Windows 2000 machine(s)
>> 2) Create and configure secondary DNS zones for appropriate dns
>> domains on these DNS servers. Configure primary servers for these
>> zones to allow replication
>> 3) Once the zone transfer was successful, reconfigure DNS servers
>> hosting the transferred zones so DNS server on W2k machine would be
>> primary server (i.e. convert the zones to primary zones).
>> Reconfigure other DNS servers to be secondary servers for these
>> zones. 4) Once other DNS servers no longer needed, remove the
>> secondary zones for appropriate dns domains from them.
>>
>> --
>> Dmitry Korolyov [d__k@removethispart.mail.ru]
>> MVP: Windows Server - Active Directory
>>
>> <anonymous@discussions.microsoft.com> wrote in message
>> news:d68a01c3ef6e$c27fc3e0$a001280a@phx.gbl...
>> I have a interesting project ahead. Our current
>> environment runs DNS on Metal IP. (Checkpoint) product).
>> Anyway with our active directory structure growing and
>> its reliance on DNS we decided it be better to go ahead
>> and move the AD zones over to windows 2000. So our
>> parent domain will remain on the existing dns platform.
>> Our subdomains for 2k will move to windows 2000. This
>> seemed simple enough until looking at it further I see
>> that the two 2k domains which are parent and child
>> domains of each other were configured as multiple zones
>> on the existing platform. So here is what I have. Our
>> parent domain zz.com will remain on the existing domain.
>> Our two 2k domains are yy.zz.com and xx.yy.zz.com. I
>> really wanted two 2k servers to be authoritive for
>> yy.zz.com domain and xx.yy.zz.com domain in a single zone
>> but since they are separate zones in the existing
>> infrastructure they migrate over as seperate zones. I
>> could try and modify the zone files manually or my other
>> option seems to be start from scratch on windows 2000
>> after delegating authority for yy.zz.com and recreating
>> the windows 2k recoreds by netdiag /fix. This will fix
>> the SRV records but my dynamic host records will have to
>> re regester. I have tried to test it out in our lab and
>> I get about half the workstations regestering. I tried
>> to ipconfig /regesterdns but that does not seem to do the
>> trick. Any Ideal would be helpful. I know this is long
>> and confusing Im sure.

In addition to Dmitry's suggestions.....

If your child zones are being hosted by the child domain's respective DNS
servers, then you may want to use a delegation, You would delegate the child
zone from the parent (or root) DNS server to the DNS server hosting the
child zone. Then you would forward from the child DNS server to the parent
DNS server. Then forward to the ISP from the parent.

255248 - HOW TO Create a Child Domain in Active Directory and Delegate the
DNS Namespace to the Child Domain:
http://support.microsoft.com/?id=255248

The delegation will separate the zone data to their respective DNS server(s)
and may be what you're looking for. In addition, not sure if the child
domains are in another site, but this would add efficiency to the child
domain's DCs and clients so that sort of traffic doesn't traverse your WAN
links.

-- 
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
-- 
=================================


Relevant Pages

  • Re: DCDIAG DNS Failure
    ... so the sddcsrv03 is a DC and DNS server right? ... My Forward zones are as follows: ... Without advance view I have 4 forward lookup zones and 7 ...
    (microsoft.public.windows.server.dns)
  • Re: DNS Recommendations w/ Active Directory & (2) DNS Servers
    ... DNS, and others stating better to use Second Server with Secondary ... while another post specifies that Stub Zones ... and the need for backup 2nd DNS server in the event our Primary Domain ... Unnecessary if you have no Secondaries -- these settings only affect ...
    (microsoft.public.windows.server.dns)
  • Re: DCDIAG DNS Failure
    ... Without advance view I have 4 forward lookup zones and 7 reverse ... My DNS server is not multihomed. ...
    (microsoft.public.windows.server.dns)
  • Re: DCDIAG DNS Failure
    ... so the sddcsrv03 is a DC and DNS server right? ... also describe your actual reverse ... and forward zones. ...
    (microsoft.public.windows.server.dns)
  • Re: Pre-authentication failed for Windows 2008 systems
    ... This posting is provided "AS IS" with no warranties, ... If you are asking if the primary DNS zone contains A ... Active Directory Integrated Zones ... There are no WINS servers configured for this interface. ...
    (microsoft.public.windows.server.security)