Dcdiag /TEST:DNS - Different results depending on which computer runs the command (same server)



  • so this is a weird one and I was hoping someone with more experience troubleshooting these issues could fill me in on whats going on.

    If I run "dcdiag /s:<domaincontroller>.pridedallas.com /TEST:DNS from my machine, I get a FAIL for RReg (errors below). If I run the same command or the simpler version "dcdiag /TEST:DNS" on the domain controller, I get a PASS for RReg. I have lots of ideas as to the cause, but can someone give me some concrete information?

    FYI everything seems to be working fine on the surface, just following up on some errors logs we saw.

    Errors

                     Network Adapter [00000010] NVIDIA nForce Networking Controller:
                     Warning:
                     Missing CNAME record at DNS server DC_IP:
                     d2da22e1-2b40-46c5-807c-76fe02ff7519._msdcs.domanname.com
    
                     Warning:
                     Missing A record at DNS server DC_IP:
                     DOMAINCONTROLLER.domanname.com
    
                     Error:
                     Missing SRV record at DNS server DC_IP:
                     _ldap._tcp.domanname.com
    
                     Error:
                     Missing SRV record at DNS server DC_IP:
                     _ldap._tcp.908f7fb4-0d70-4fce-a693-af582671bcf3.domains._msdcs.domanname.com
    
                     Error:
                     Missing SRV record at DNS server DC_IP:
                     _kerberos._tcp.dc._msdcs.domanname.com
    
                     Error:
                     Missing SRV record at DNS server DC_IP:
                     _ldap._tcp.dc._msdcs.domanname.com
    
                     Error:
                     Missing SRV record at DNS server DC_IP:
                     _kerberos._tcp.domanname.com
    
                     Error:
                     Missing SRV record at DNS server DC_IP:
                     _kerberos._udp.domanname.com
    
                     Error:
                     Missing SRV record at DNS server DC_IP:
                     _kpasswd._tcp.domanname.com
    
                     Error:
                     Missing SRV record at DNS server DC_IP:
                     _ldap._tcp.Dallas._sites.domanname.com
    
                     Error:
                     Missing SRV record at DNS server DC_IP:
                     _kerberos._tcp.Dallas._sites.dc._msdcs.domanname.com
    
                     Error:
                     Missing SRV record at DNS server DC_IP:
                     _ldap._tcp.Dallas._sites.dc._msdcs.domanname.com
    
                     Error:
                     Missing SRV record at DNS server DC_IP:
                     _kerberos._tcp.Dallas._sites.domanname.com
    
                     Error:
                     Missing SRV record at DNS server DC_IP:
                     _ldap._tcp.gc._msdcs.domanname.com
    
                     Warning:
                     Missing A record at DNS server DC_IP:
                     gc._msdcs.domanname.com
    
                     Error:
                     Missing SRV record at DNS server DC_IP:
                     _gc._tcp.Dallas._sites.domanname.com
    
                     Error:
                     Missing SRV record at DNS server DC_IP:
                     _ldap._tcp.Dallas._sites.gc._msdcs.domanname.com
    
                     Error:
                     Missing SRV record at DNS server DC_IP:
                     _ldap._tcp.pdc._msdcs.domanname.com
    
               Error: Record registrations cannot be found for all the network adapters


  • I don't know if it's the same problem or not, but I have an old AD infrastructure here. It started with Windows 200 and has been upgraded over the years. Newer versions of AD have wanted new subfolders in DNS that the upgrade (AD Forest Prep/AD Domain Prep) never took care of automatically.

    I suggest looking for a MS document on what entries are suppose to be in DNS and look for what you are missing. I was missing an entire branch. Once I created it by hand, my issues went away.



  • @Dashrender said in Dcdiag /TEST:DNS - Different results depending on which computer runs the command (same server):

    I don't know if it's the same problem or not, but I have an old AD infrastructure here. It started with Windows 200 and has been upgraded over the years. Newer versions of AD have wanted new subfolders in DNS that the upgrade (AD Forest Prep/AD Domain Prep) never took care of automatically.

    I suggest looking for a MS document on what entries are suppose to be in DNS and look for what you are missing. I was missing an entire branch. Once I created it by hand, my issues went away.

    interesting. Did you also have the discrepancy where it produces 2 different results depending on which machine runs the command?



  • Honestly can't recall - it was around 4 years ago that it happened to me.

    I suppose there could be a post on Spiceworks about it.


Log in to reply