Aico
asked on
Replication problems with AD
We've got the following situation:
domain1.com with three domain controllers distributed over three countries.
In every country 1 child domain with two domain controllers.
The three domain controllers all have secondary DNS zones of the other countries and child domains. DNS resolution works fine.
The following error occurs on one of my root domain controllers:
The DSA operation is unable to proceed because of a DNS lookup failure. The record data is the status code. The operation will be retried.
I've tried the following without any results:
- Recreated secondary DNS zones.
- Flushed DNS caches on all the domain controllers.
But still the error occurs.
Any idea's?
domain1.com with three domain controllers distributed over three countries.
In every country 1 child domain with two domain controllers.
The three domain controllers all have secondary DNS zones of the other countries and child domains. DNS resolution works fine.
The following error occurs on one of my root domain controllers:
The DSA operation is unable to proceed because of a DNS lookup failure. The record data is the status code. The operation will be retried.
I've tried the following without any results:
- Recreated secondary DNS zones.
- Flushed DNS caches on all the domain controllers.
But still the error occurs.
Any idea's?
Anything in the event viewer..?
I didn't hear you mentioning PDC's and BDC's (arrgghh-win2k is so much better) but, just in case; a new svrmngr for mixed domains:
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q249140
This one is just dumb, but, it can't hurt to take a peak: Basically make sure the preffered DNS IP address IS correct.
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q263624
This one is interesting:Invovles Large group Update Scenario
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q289168
Another interesting one:
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q272279
and finally a workaround: Enable loose replication, disable it after replication completes:
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q317097
Hope one of those helps you.
Cheers.
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q249140
This one is just dumb, but, it can't hurt to take a peak: Basically make sure the preffered DNS IP address IS correct.
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q263624
This one is interesting:Invovles Large group Update Scenario
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q289168
Another interesting one:
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q272279
and finally a workaround: Enable loose replication, disable it after replication completes:
http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q317097
Hope one of those helps you.
Cheers.
Do you have your replication defined in Sites and Services or are you letting it do it automatically?
ASKER
What do you mean? Do you mean do I use automatically generated connections or manual connections. If yes, both. Some connections could not be created automatically for some reason, so I created them manually. When I check replication topology everything checks out fine.
It says there is a DNS lookup failure...
Try using either the NSLOOKUP tool or try using the builtin DNS diagnostics in the DNS manager MMC snap-in. Try doing lookups from one server to the other.
Try using either the NSLOOKUP tool or try using the builtin DNS diagnostics in the DNS manager MMC snap-in. Try doing lookups from one server to the other.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok, I will try that and let you know how it turns out. Thanx for the input.
ASKER
Sorry for the late reply. Haven't had problems anymore, so just checking back to close the question.