Hello,

We have 4 DC on 4 sites (3 are W2K and one is 2003). One the main site we
have a W2K DC which owns the 5 FSMO roles.

Recently the sites are diseappearing randomly from the DNS (one site
disappears or more) Forward Lookup Zones (under SERVERNAME\Forward Lookup
Zones\DOMAINNAME\_MSDCS\DC\_SITES and also under SERVERNAME\Forward Lookup
Zones\DOMAINNAME\_SITES and this leads to replication failures.

To correct the situation we run NETDIAG /FIX on each DC and the replication
restarts and takes over (we also use dssite.msc to make things happen
faster). But after about 24 hours the problem is back. We get event ID 1311
and 1566 - NTDS KCC. However the network throughput looks good.

How would you troubleshoot the source of such a problem ? To me it seem like
one DNS is causing the records to diseappear and then replicates to the
other DNS.

Regards,

Hi
For 1311
Ensure all sites belong to at least one site link. Make sure the site links
provide a path between all domain controllers containing a replica of a
given directory partition. Make sure "Bridge All Site Links" is set
correctly. If you have manually assigned preferred bridge-head servers, make
sure they are online.

Event ID 1311: Replication configuration does not reflect the physical
network

http://technet2.microsoft.com/Window....mspx?mfr=true

The 1566 is related with the 1311 means that the one or more DCs are
unavailable

Now because you've a problem with the zones, that can be the cause of you
replication errors.
When Zones diseappear, generaly means that you've duplicated zones, can you
expplain how dns is setup in your existing DNS servers.

--
I hope that the information above s you

Good Luck
Jorge Silva
MCSA
Systems Administrator
"Jacques Trépanier" <zx_jacques@hotmail.com> wrote in message
news:ufd62Pu9GHA.2288@TK2MSFTNGP05.phx.gbl...
> Hello,
>
> We have 4 DC on 4 sites (3 are W2K and one is 2003). One the main site we
> have a W2K DC which owns the 5 FSMO roles.
>
> Recently the sites are diseappearing randomly from the DNS (one site
> disappears or more) Forward Lookup Zones (under SERVERNAME\Forward Lookup
> Zones\DOMAINNAME\_MSDCS\DC\_SITES and also under SERVERNAME\Forward Lookup
> Zones\DOMAINNAME\_SITES and this leads to replication failures.
>
> To correct the situation we run NETDIAG /FIX on each DC and the
> replication restarts and takes over (we also use dssite.msc to make things
> happen faster). But after about 24 hours the problem is back. We get event
> ID 1311 and 1566 - NTDS KCC. However the network throughput looks good.
>
> How would you troubleshoot the source of such a problem ? To me it seem
> like one DNS is causing the records to diseappear and then replicates to
> the other DNS.
>
> Regards,
>
>

Jorge,

Each DC has a DNS which is AD integrated. Basically all DNS info, for LAN
name resolution is on the 4 DC. For external name resolution (internet) we
have 2 other member servers.

Regards,


"Jorge Silva" <jorgesilva_pt@hotmail.com> a écrit dans le message de news:
e$DMFEv9GHA.4740@TK2MSFTNGP03.phx.gbl...
> Hi
> For 1311
> Ensure all sites belong to at least one site link. Make sure the site
> links provide a path between all domain controllers containing a replica
> of a given directory partition. Make sure "Bridge All Site Links" is set
> correctly. If you have manually assigned preferred bridge-head servers,
> make sure they are online.
>
> Event ID 1311: Replication configuration does not reflect the physical
> network
>
> http://technet2.microsoft.com/Window....mspx?mfr=true
>
> The 1566 is related with the 1311 means that the one or more DCs are
> unavailable
>
> Now because you've a problem with the zones, that can be the cause of you
> replication errors.
> When Zones diseappear, generaly means that you've duplicated zones, can
> you expplain how dns is setup in your existing DNS servers.
>
> --
> I hope that the information above s you
>
> Good Luck
> Jorge Silva
> MCSA
> Systems Administrator
> "Jacques Trépanier" <zx_jacques@hotmail.com> wrote in message
> news:ufd62Pu9GHA.2288@TK2MSFTNGP05.phx.gbl...
>> Hello,
>>
>> We have 4 DC on 4 sites (3 are W2K and one is 2003). One the main site we
>> have a W2K DC which owns the 5 FSMO roles.
>>
>> Recently the sites are diseappearing randomly from the DNS (one site
>> disappears or more) Forward Lookup Zones (under SERVERNAME\Forward Lookup
>> Zones\DOMAINNAME\_MSDCS\DC\_SITES and also under SERVERNAME\Forward
>> Lookup Zones\DOMAINNAME\_SITES and this leads to replication failures.
>>
>> To correct the situation we run NETDIAG /FIX on each DC and the
>> replication restarts and takes over (we also use dssite.msc to make
>> things happen faster). But after about 24 hours the problem is back. We
>> get event ID 1311 and 1566 - NTDS KCC. However the network throughput
>> looks good.
>>
>> How would you troubleshoot the source of such a problem ? To me it seem
>> like one DNS is causing the records to diseappear and then replicates to
>> the other DNS.
>>
>> Regards,
>>
>>
>
>

NETDIAG /TESTNS fails on 2 servers with this (shown only section in error)

DNS test . . . . . . . . . . . . . : Failed
[WARNING]: The DNS registration for 'syst0101.bellnordiq.net'
is
orrect only on some DNS servers.
Please wait 15 min for replication and run the test
again.
[WARNING] The DNS entries for this DC are not registered correctly on
DNS s
rver '10.212.7.7'. Please wait for 30 minutes for DNS server replication.
[WARNING] The DNS entries for this DC are not registered correctly on
DNS s
rver '10.212.127.42'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.

Waiting 45 minutes doesn`t change anything. This is on 2 W2K DC the 2
without FSMO roles.


"Jacques Trépanier" <zx_jacques@hotmail.com> a écrit dans le message de
news: OXFJMN39GHA.5092@TK2MSFTNGP04.phx.gbl...
> Jorge,
>
> Each DC has a DNS which is AD integrated. Basically all DNS info, for LAN
> name resolution is on the 4 DC. For external name resolution (internet) we
> have 2 other member servers.
>
> Regards,
>
>
> "Jorge Silva" <jorgesilva_pt@hotmail.com> a écrit dans le message de news:
> e$DMFEv9GHA.4740@TK2MSFTNGP03.phx.gbl...
>> Hi
>> For 1311
>> Ensure all sites belong to at least one site link. Make sure the site
>> links provide a path between all domain controllers containing a replica
>> of a given directory partition. Make sure "Bridge All Site Links" is set
>> correctly. If you have manually assigned preferred bridge-head servers,
>> make sure they are online.
>>
>> Event ID 1311: Replication configuration does not reflect the physical
>> network
>>
>> http://technet2.microsoft.com/Window....mspx?mfr=true
>>
>> The 1566 is related with the 1311 means that the one or more DCs are
>> unavailable
>>
>> Now because you've a problem with the zones, that can be the cause of you
>> replication errors.
>> When Zones diseappear, generaly means that you've duplicated zones, can
>> you expplain how dns is setup in your existing DNS servers.
>>
>> --
>> I hope that the information above s you
>>
>> Good Luck
>> Jorge Silva
>> MCSA
>> Systems Administrator
>> "Jacques Trépanier" <zx_jacques@hotmail.com> wrote in message
>> news:ufd62Pu9GHA.2288@TK2MSFTNGP05.phx.gbl...
>>> Hello,
>>>
>>> We have 4 DC on 4 sites (3 are W2K and one is 2003). One the main site
>>> we have a W2K DC which owns the 5 FSMO roles.
>>>
>>> Recently the sites are diseappearing randomly from the DNS (one site
>>> disappears or more) Forward Lookup Zones (under SERVERNAME\Forward
>>> Lookup Zones\DOMAINNAME\_MSDCS\DC\_SITES and also under
>>> SERVERNAME\Forward Lookup Zones\DOMAINNAME\_SITES and this leads to
>>> replication failures.
>>>
>>> To correct the situation we run NETDIAG /FIX on each DC and the
>>> replication restarts and takes over (we also use dssite.msc to make
>>> things happen faster). But after about 24 hours the problem is back. We
>>> get event ID 1311 and 1566 - NTDS KCC. However the network throughput
>>> looks good.
>>>
>>> How would you troubleshoot the source of such a problem ? To me it seem
>>> like one DNS is causing the records to diseappear and then replicates to
>>> the other DNS.
>>>
>>> Regards,
>>>
>>>
>>
>>
>
>

Hi
make sure that these servers point to a valid internal DNS server, and that
the zone accepts dynamic updates.

--
I hope that the information above s you

Good Luck
Jorge Silva
MCSA
Systems Administrator
"Jacques Trépanier" <zx_jacques@hotmail.com> wrote in message
news:elXhg%2369GHA.3860@TK2MSFTNGP02.phx.gbl...
> NETDIAG /TESTNS fails on 2 servers with this (shown only section in
> error)
>
> DNS test . . . . . . . . . . . . . : Failed
> [WARNING]: The DNS registration for 'syst0101.bellnordiq.net'
> is
> orrect only on some DNS servers.
> Please wait 15 min for replication and run the test
> again.
> [WARNING] The DNS entries for this DC are not registered correctly on
> DNS s
> rver '10.212.7.7'. Please wait for 30 minutes for DNS server replication.
> [WARNING] The DNS entries for this DC are not registered correctly on
> DNS s
> rver '10.212.127.42'. Please wait for 30 minutes for DNS server
> replication.
> [FATAL] No DNS servers have the DNS records for this DC registered.
>
> Waiting 45 minutes doesn`t change anything. This is on 2 W2K DC the 2
> without FSMO roles.
>
>
> "Jacques Trépanier" <zx_jacques@hotmail.com> a écrit dans le message de
> news: OXFJMN39GHA.5092@TK2MSFTNGP04.phx.gbl...
>> Jorge,
>>
>> Each DC has a DNS which is AD integrated. Basically all DNS info, for LAN
>> name resolution is on the 4 DC. For external name resolution (internet)
>> we have 2 other member servers.
>>
>> Regards,
>>
>>
>> "Jorge Silva" <jorgesilva_pt@hotmail.com> a écrit dans le message de
>> news: e$DMFEv9GHA.4740@TK2MSFTNGP03.phx.gbl...
>>> Hi
>>> For 1311
>>> Ensure all sites belong to at least one site link. Make sure the site
>>> links provide a path between all domain controllers containing a replica
>>> of a given directory partition. Make sure "Bridge All Site Links" is set
>>> correctly. If you have manually assigned preferred bridge-head servers,
>>> make sure they are online.
>>>
>>> Event ID 1311: Replication configuration does not reflect the physical
>>> network
>>>
>>> http://technet2.microsoft.com/Window....mspx?mfr=true
>>>
>>> The 1566 is related with the 1311 means that the one or more DCs are
>>> unavailable
>>>
>>> Now because you've a problem with the zones, that can be the cause of
>>> you replication errors.
>>> When Zones diseappear, generaly means that you've duplicated zones, can
>>> you expplain how dns is setup in your existing DNS servers.
>>>
>>> --
>>> I hope that the information above s you
>>>
>>> Good Luck
>>> Jorge Silva
>>> MCSA
>>> Systems Administrator
>>> "Jacques Trépanier" <zx_jacques@hotmail.com> wrote in message
>>> news:ufd62Pu9GHA.2288@TK2MSFTNGP05.phx.gbl...
>>>> Hello,
>>>>
>>>> We have 4 DC on 4 sites (3 are W2K and one is 2003). One the main site
>>>> we have a W2K DC which owns the 5 FSMO roles.
>>>>
>>>> Recently the sites are diseappearing randomly from the DNS (one site
>>>> disappears or more) Forward Lookup Zones (under SERVERNAME\Forward
>>>> Lookup Zones\DOMAINNAME\_MSDCS\DC\_SITES and also under
>>>> SERVERNAME\Forward Lookup Zones\DOMAINNAME\_SITES and this leads to
>>>> replication failures.
>>>>
>>>> To correct the situation we run NETDIAG /FIX on each DC and the
>>>> replication restarts and takes over (we also use dssite.msc to make
>>>> things happen faster). But after about 24 hours the problem is back. We
>>>> get event ID 1311 and 1566 - NTDS KCC. However the network throughput
>>>> looks good.
>>>>
>>>> How would you troubleshoot the source of such a problem ? To me it seem
>>>> like one DNS is causing the records to diseappear and then replicates
>>>> to the other DNS.
>>>>
>>>> Regards,
>>>>
>>>>
>>>
>>>
>>
>>
>
>