Re: Server 2003 DNS ADI import or sync? WHat are my options

If I setup the zones to replicate, how do I insure that the records from the
ROOT zone populate to CORP_A, and not the other way around?

My nightmare, and this comes from ignorance of the tools in use here, is
that all of the sudden, in the replication, the CORP_A sources tells all the
records in ROOT to "take a hike", ROOT then syncs with what CORP_A has and it
empties my DNS info in ROOT... and then I've lost the records.

nightmare and high drama... ;)




"Chris Dent [MVP]" wrote:


I suspect then that you have two versions of the same zone.

What version of Windows runs on CORP_A DC? If it's Windows 2000 it's easily
explained because the Replication Scope used on the Root servers is only
compatible with Windows 2003.

Basically, you have a version here (approximately, depending on actual
naming):

CN=MicrosoftDNS,CN=System,DC=Corp_A,DC=Root,DC=local

And a version here:

DC=ForestDNSZones,DC=Root,DC=local

Given that you have two entirely separate zones merging them won't really
work. Which is more complete right now?

If you find the verison on Corp_A is the one you wish to keep the version in
the Root should be deleted. This shouldn't have an impact on the version
running on Corp_A (but it's worth taking a backup of the zone, just in
case). Then if Corp_A is running 2003 Server you can switch the Zone
replication there to All DNS Servers in the Forest and allow that to
replicate.

--
Chris Dent
MVP Directory Services


"Craig Tate" <Craig Tate@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:72445D53-72F6-4497-96C8-68C7EF6FD694@xxxxxxxxxxxxxxxx
More info on this

From the 2 DC/DNS servers in ROOT, their replication is set up as "All DNS
Servers in the Active Directory forest" when reight clicking on the shild
CORP_A domain.

But if I select a CORP_A DC/DNS server, and look at the DNS settings, the
replication is setup as "All domain controllers in the Active Directory
domain".

Also, I am unclear on how SOA records play any role with ADI DNS, can
someone throw me a bone? :)




.

Relevant Pages

  • Re: need help,not your average dns problem
    ... thanks for the reply but no I do not have a root zone and it should not be a ... resolve names via root servers. ... AD zones on these Servers and all dns requests they cannot resolve ... When moved to Windows Active Directory 7 years ago, ...
    (microsoft.public.windows.server.dns)
  • Re: Problems with named default configuration in 6-STABLE
    ... transfer the zone, the hints mechanism is still in the comments. ... with overall root traffic for the root zone, ... I should add for the sake of completeness that not every DNS ... have 5 servers to choose from (and we only need one good transfer to ...
    (freebsd-stable)
  • Re: AD 2003 Design from NT 4
    ... created the zone xxx-domain.com, with dynamic and replicate to all DNS servers in the domain. ... that is where the problem is, the replication scope of the second domain. ... NC Partition, and also in the DomainDnsZones App ...
    (microsoft.public.windows.server.dns)
  • Re: Trust Relationship Between 2 Domains
    ... All servers except 1 server appeared in the DNS zone of Domain B in Domain ... ACTIVE DIRECTORY FOREST" However in Domain B the same zone's replication ...
    (microsoft.public.windows.server.migration)
  • Re: Problems with named default configuration in 6-STABLE
    ... transfer the zone, the hints mechanism is still in the comments. ... with overall root traffic for the root zone, ... slaving the root zone will make you still being able to resolve DNS ... servers worldwide being unreachable. ...
    (freebsd-stable)