Replication problems with errors

[Keith]

HELP!

I have a windows 2000 domain. It consists of 1 global
catalog server and 3 other Domain controllers. One domain
controller is constantly getting 2 different errors. The
first is in the Directory Service event viewer:

Event 1265: The attempt to establish a replication link
with parameters:

Inter-site Transport (if any): failed with the following
status:

The DSA operation is unable to proceed because of a DNS
lookup failure.

From everything i can find in MS knowledgebase and other
sources this points to a DNS problem. In looking that up i
found another error that i was recieving.

Event 5781: Dynamic registration or deregistration of one
or more DNS records failed because no DNS servers are
available.

I have tried every trouble shooting technique that MS has
to offer. It seems that because of this, this domain
controller is not replicating with the Global Catalog
server. I ran the Replication monitor and it reported a
problem.

Any thoughts?

 

[Ace Fekay [MVP]]

In

HELP!

I have a windows 2000 domain. It consists of 1 global
catalog server and 3 other Domain controllers. One domain
controller is constantly getting 2 different errors. The
first is in the Directory Service event viewer:

Event 1265: The attempt to establish a replication link
with parameters:

Inter-site Transport (if any): failed with the following
status:

The DSA operation is unable to proceed because of a DNS
lookup failure.

From everything i can find in MS knowledgebase and other
sources this points to a DNS problem. In looking that up i
found another error that i was recieving.

Event 5781: Dynamic registration or deregistration of one
or more DNS records failed because no DNS servers are
available.

I have tried every trouble shooting technique that MS has
to offer. It seems that because of this, this domain
controller is not replicating with the Global Catalog
server. I ran the Replication monitor and it reported a
problem.

Any thoughts?

Could be one of two things:

1. If you are using an external DNS in your IP properties (of DCs and
clients), major issues will occur, such as this. Recommended to ONLY use
theinternal DNS that is hosting your AD zone. Recommended to use a forwarder
for efficient Internet name resolution, as shown how to here:
http://support.microsoft.com/?id=300202

2. You have SP4 installed and your AD DNS Domain name is a single label name
('domain' rather than the required format of 'domain.com').

If you can post an unedited ipconfig /all of the three DCs, that would be of
great benefit to diagnose this and usually will help us in 95% of the time
to come up with a resolve.


--
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

 

[Systems Administrator]

Thanks all for the info. I have the exact same error messages (1265 and
5781) with the same scenario. I have 1 Global Catalog server and 1
additional DC. They both point to same DNS server (another W2K DNS server)
in their IP properties. They both can ping each other by names and it
returned the FQDN just fine. However, when I make a change (user account,
logon script, etc..) on the DC, it does not replicate to the Global Catalog
server with the same errors of listed above. Do the DC servers must run
it's own DNS service? If so, the article (id=300202) you listed notes that
DC servers should "not" point to itself for DNS, if this is true, then my
"current" scenario applies because they both point to another DNS server,
but it's not working right because of problems mentioned. Any advice is
greatly appreciated. Please help to explain clearly as I'm very novice in
terms of DNS.

Regards.

"Ace Fekay [MVP]"

 

[Ace Fekay [MVP]]

In

Thanks all for the info. I have the exact same error messages (1265
and 5781) with the same scenario. I have 1 Global Catalog server and
1 additional DC. They both point to same DNS server (another W2K DNS
server) in their IP properties. They both can ping each other by
names and it returned the FQDN just fine. However, when I make a
change (user account, logon script, etc..) on the DC, it does not
replicate to the Global Catalog server with the same errors of listed
above. Do the DC servers must run it's own DNS service? If so, the
article (id=300202) you listed notes that DC servers should "not"
point to itself for DNS, if this is true, then my "current" scenario
applies because they both point to another DNS server, but it's not
working right because of problems mentioned. Any advice is greatly
appreciated. Please help to explain clearly as I'm very novice in
terms of DNS.

Regards.

1265 can be caused by a number of things.
http://www.eventid.net/display.asp?eventid=1265&source=
5781's too:
http://www.eventid.net/display.asp?eventid=5781&source=


So, due to the errors, and not enough info provided by yourself, and due to
the range of causes of these errors, at this point, as I mentioned, we'll
definitely need to see an unedited ipconfig /all from both DCs to eliminate
the guess work.

As for as using a different DNS server that's a non-DC, that is no problem.
As long as only you use that DNS server and not your ISP's. You can also
opt, which is the recommended secure method, to install DNS on both DCs and
use both of them, and make the zone AD Integrated. THis will give you
security and fault tolerance. And YES, it's recommended if you have two such
as this, to not point to itself for the first entry, but rather it's partner
as the first entry and make the second entry as itself. That eliminates
other errors. But if you only have the one, then no biggy...

--
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

 

[Kevin D. Goodknecht [MVP]]

In Keith <[email protected]> posted a question
Then Kevin replied below:
: HELP!
:
: I have a windows 2000 domain. It consists of 1 global
: catalog server and 3 other Domain controllers. One domain
: controller is constantly getting 2 different errors. The
: first is in the Directory Service event viewer:
:
: Event 1265: The attempt to establish a replication link
: with parameters:
:
: Inter-site Transport (if any): failed with the following
: status:
:
: The DSA operation is unable to proceed because of a DNS
: lookup failure.
:
: From everything i can find in MS knowledgebase and other
: sources this points to a DNS problem. In looking that up i
: found another error that i was recieving.
:
: Event 5781: Dynamic registration or deregistration of one
: or more DNS records failed because no DNS servers are
: available.
:
: I have tried every trouble shooting technique that MS has
: to offer. It seems that because of this, this domain
: controller is not replicating with the Global Catalog
: server. I ran the Replication monitor and it reported a
: problem.
:
: Any thoughts?

Can you post an ipconfig /all from this DC and the AD DNS Domain name?
Run netdiag /fix and netdiag /v note the errors you get.