Duplicate _ldap._tcp.pdc._msdcs.<domain> service records

[Guest]

We are deploying an application that for some reason is having a problem
authenticating its domain credentials. Although there is "nothing" wrong
when authenticating manually, the prog fails to execute. The developer
suggested that there is a possibility that there is a prob with the PDC
Emulator role. He generated the following query and got this result;

set type=SRV
_ldap._tcp.pdc._msdcs.icm.bce.ca

result:

_ldap._tcp.pdc._msdcs.icm.bce.ca
svr hostname = dmoci3.icm.bce.ca
_ldap._tcp.pdc._msdcs.icm.bce.ca
svr hostname = dc2cpp.icm.bce.ca

Both servers are DCs in the domain, host DC2CPP is the server that currently
has the PDC Emulator FSMO role. Is there are reason for the duplicate entry
and should the other entry be removed?

 

[Kevin D. Goodknecht Sr. [MVP]]

We are deploying an application that for some reason is having a
problem authenticating its domain credentials. Although there is
"nothing" wrong when authenticating manually, the prog fails to
execute. The developer suggested that there is a possibility that
there is a prob with the PDC Emulator role. He generated the
following query and got this result;


result:

_ldap._tcp.pdc._msdcs.icm.bce.ca
svr hostname = dmoci3.icm.bce.ca
_ldap._tcp.pdc._msdcs.icm.bce.ca
svr hostname = dc2cpp.icm.bce.ca

Both servers are DCs in the domain, host DC2CPP is the server that
currently has the PDC Emulator FSMO role. Is there are reason for
the duplicate entry and should the other entry be removed?

There is no reason I can think of, there can only be one PDC emulator, in a
domain. Yes, delete the record, restart the netlogon service on that DC to
see if it is reregistered.