Replication problem

  • Thread starter Thread starter Bill
  • Start date Start date
B

Bill

I am experiencing slow replication down the tree and no
replication towards the root.

repadmin /showreps shows no outbound replication
partners. Inbound replication is fine.

Dcdiag reports that <dcguid>._msdcs.domain.com couldn't
be resolved, the server name <server.domain.com> resolved
to the ipaddress <xxx.xxx.x.xxx> and was pingable. Check
that the address is registered correctly with the DNS
server.

I know that this is probably DNS related. I ran DNSLINT
and it reports that

CNAME records for forest GUIDs not found:
GUID: <same dcguid as above>._msdcs.domain.com
DC:<same DC as above>

Replmon does not report any errors.

Questions:

How can I register the CNAME for the
<dcguid>._msdcs.domain.com?
 
You can register all applicable DNS records by restarting the netlogon
service (providing the DHCP client service is running -even though you're
not 'actually' using it).

The main question here is how, exactly, DNS is setup throughout the tree??
We might be better equipped to offer helpful advice with a description of
how you've implemented DNS.

If your DC points to itself for DNS, point it at one of the other (working)
DC/DNS servers before restarting -it can happen that you'll update (the
records) on the local DC but the others still can't see it and the local
still can't push. Therefore, with these kind of issues, the best thing is
to *temporarily* point to another DC.


--

Paul Williams
_________________________________________
http://www.msresource.net


Join us in our new forums!
http://forums.msresource.net
_________________________________________


I am experiencing slow replication down the tree and no
replication towards the root.

repadmin /showreps shows no outbound replication
partners. Inbound replication is fine.

Dcdiag reports that <dcguid>._msdcs.domain.com couldn't
be resolved, the server name <server.domain.com> resolved
to the ipaddress <xxx.xxx.x.xxx> and was pingable. Check
that the address is registered correctly with the DNS
server.

I know that this is probably DNS related. I ran DNSLINT
and it reports that

CNAME records for forest GUIDs not found:
GUID: <same dcguid as above>._msdcs.domain.com
DC:<same DC as above>

Replmon does not report any errors.

Questions:

How can I register the CNAME for the
<dcguid>._msdcs.domain.com?
 
Thanks Paul,

We are using BIND for secondaries. The DC's are pointing
to themselves. (after DNS is installed). And they are
pointing to the BIND server as the second DNS server.

What we did was aquire another company and were using
their DHCP during the DC setup. After they were on our
network, we shut down their DHCP server and put the scope
in our own.

I have done several of these types of migrations, but
have never had this come up.

Could the DHCP server change cause this problem?
Could the problem be caused by our using a tunnel or
replication? It seems to work okay at other locations and
all ports are open.

Thanks,
Bill
 
Back
Top