I am noticing an issue when running dcdiag from our domain controllers. In the DNS tests for each DC there is a warning about missing SRV records. When looking through DNS I am seeing the SRV records for each DC but in a different location then what Dcdiag seems to be expecting. Searching for the SRV records of the domain through nslookup is also returning the records found in DNS. The location in which these records are held seem to be in a different spot then what dcdiag is expecting. The guid that dcdiag mentions in the errors matches the guid for the domain but is not what is seen in DNS. Right now functionality seems to be fine as no issues regarding this has come up. Is this mismatch of guids between what is seen in DNS and the domain going to be an issue? Is there a solution for this that can be easily resolved?
The warning from the dcdiag dns test reads:
Error:
Missing SRV record at DNS server XX.XX.XX.XX:
_ldap._tcp.b152358d-93c6-44e2-80e1-d924e906394c.domains._msdcs.domain.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
UPDATE: It seems that the GUID seen in DNS is the GUID of the Domain when queried from CIM or WMI. Why would this be a different GUID from ADSI?



