DC name not resolving in Recipient Update Service

I had been getting the errors  8026 and 8062, "

LDAP Bind was unsuccessful on directory dc.domain.com for distinguished name ''. Directory returned error:[0x51] Server Down.  DC=,DC=com

And I checked out all of the other suggestions.  When i went into the RUS to select a DC, it won't allow me to select what I consider to be my Primary DC.  It resolves the other one, but not this one.  I successfully pinged the DC, same with nslookup.  I had been having DNS issues, but what can I do to resolve this?

 
IDPIncAsked:
Who is Participating?
 
SembeeConnect With a Mentor Commented:
There are always two RUS settings. What you are seeing is normal.
Is this a single domain environment or child/parent?

All domain controllers are equal. As long as the domain controller listed is the accessible and is quite close then it shouldn't matter which server is being used, as long as it is valid.

Simon.
0
 
SembeeCommented:
Is that server a global catalog? Exchange will only use global catalogs for its DC functionality.

Simon.
0
 
IDPIncAuthor Commented:
Yes, both DC's are GC's
0
 
IDPIncAuthor Commented:
Clarification.  We have two RUS's  the Enterprise COnfiguration, and then the domain related one in the second position.  The Enterprise one seems to resolve just fine, but the second one does not.  These were created before me.  Are two of them necessary?  Again I don't want to break more than I fix.  
0
 
IDPIncAuthor Commented:
Single domain environment.  
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.