Re: Replication problem


Hi,

Okie. The steps that I took were:

1.) Install and configure DNS forward lookup zone and reverse lookup zone and
add A record for the DNS server.
2.) Set NIC to point to itself as DNS.
3.) Run dcpromo to promote that DNS server into first DC of a new forest,
namely root domain.
4.) Install and configure DNS forward lookup zone and reverse lookup zone for
child domain which is to be promoted.
5.) Set NIC to point to root DC as DNS.
6.) Run dcpromo to promote child domain to be DC of an existing forest,
namely child domain.
7.) Enable Global Catalog checkbox for child domain in Active Directory Sites
and Services in child DC.
8.) Enable Global Catalog checkbox for child domain in Actuve Directory Sites
and Services in root DC.
9.) Enable Active Directory Replication for entire forest for forward lookup
zone and reverse lookup zone for both root DC and child DC.

I tried with steps similar to steps illustrated above before and it worked
well such that I didn't need to use secondary zone, stub zone or forwarder
for both root and child domain for name resolution, but today when I
installed a fresh copy to simulate again, it didn't work. Thus, I think
there is some steps that I miss, but just couldn't figure it out.

Thanks.


Ace Fekay [MVP] wrote:
>In news:51BB2F1D7C6B2@xxxxxxxxxxxxxxx,
>kevin via WinServerKB.com <forum@xxxxxxxxxxxxxxx> stated, which I then
>commented on below:
>> Hi,
>>
>[quoted text clipped - 9 lines]
>>
>> Thanks.
>
>Did you also verify replication errors by checking if there are any
>replication errors in the Event log of any of your DCs?
>Did you use replmon to verify that as well?
>
>IT would be helpful to know how your infrastructure is setup, such as are
>you delegating the child zone to the child DNS servers, or are you using a
>single namespace replicated forest wide?
>
>If you are delegating, or using stubs, when a host in a child domain
>registers it's record into the child zone, such as (for example):
>child.domain.com,
>then that record or host stays in that zone. If it is delegated or stubbed,
>you will NOT see that record in the forest root DNS server, but rather a
>reference to the DNS server(s) that host the child zone.
>
>If the zone is set in the ForestDnsZones app partition, and you chose to add
>it as a separate namespace in the DNS server(s) in the forest root, then you
>will see it as a separate namespace, but if it is delegated, it won't allow
>you to do that.
>
>Maybe it would be extremely helpful if you can provide more specific
>information.
>


--
Message posted via WinServerKB.com
http://www.winserverkb.com/Uwe/Forums.aspx/windows-server-dns/200507/1
.

Relevant Pages

  • Re: DNS Redesign Issue
    ... This is because tbe TLD DNS server is the only ... set the new child domain DNS server as primary for the domain controllers? ... -Using DNS console you can right-click the zone and export to a File, ...
    (microsoft.public.windows.server.dns)
  • Re: DNS Redesign Issue
    ... set the new child domain DNS server as primary for the domain controllers? ... -If you are going to create a new AD Integrated Zone in each child domain, ...
    (microsoft.public.windows.server.dns)
  • Re: DNS Redesign Issue
    ... -Using DNS console you can right-click the zone and export to a File, ... -To export a Zone and import that Zone in another DNS Server you need to use ... Create a child zone dallas on the DNS server in the child domain ...
    (microsoft.public.windows.server.dns)
  • Re: DNS Redesign Issue
    ... -Using DNS console you can right-click the zone and export to a File, ... -To export a Zone and import that Zone in another DNS Server you need to use ... Create a child zone dallas on the DNS server in the child domain ...
    (microsoft.public.windows.server.dns)
  • Re: Create a child domain in AD and delegate the DNS namespace
    ... You also might want to create a stub zone on the parent DNS Server.... ... > delegate the child domain zone to the DNS server in the new child ... point the new servers primary DNS server to your parent DNS server. ...
    (microsoft.public.windows.server.dns)