Quantcast
Channel: Network Infrastructure Servers forum
Viewing all articles
Browse latest Browse all 5877

Static DNS Record disappearing

$
0
0

Good Morning,

I am the Network Administrator for a small non-profit organization.  We ran into an issue a while back that caused me to discover that at least one static DNS record in our organization vanished.  Unfortunately, this DNS record belongs to a mission critical server so it caused a few headaches along the way.  Once I re-added the DNS entry, I ran dcdiag.exe and found the following. 

I've been in the process of decommissioning Server1 and have moved critical services off of it.  This issue began after I disconnected it from the network for a few hours to see if any of our devices were soley dependent on it for DNS.  Once I validated that the environment was generally good to go, (although we were seeing some minor latency due to devices trying to hit Server1 before moving onto Server2 for DNS entries) I reconnected it. I've since restarted Server1 and forced replication to see if that cleared the issue, but I'm still seeing this.

I'd appreciate any assistance you could provide.

Command Line: "dcdiag.exe /v /c /d /e /s:server2"

Starting test: VerifyEnterpriseReferences

         The following problems were found while verifying various important DN

         references.  Note, that  these problems can be reported because of

         latency in replication.  So follow up to resolve the following

         problems, only if the same problem is reported on all DCs for a given

         domain or if  the problem persists after replication has had

         reasonable time to replicate changes.
            [1] Problem: Missing Expected Value

             Base Object: CN=SERVER1,OU=Domain Controllers,DC=MOF,DC=ORG

             Base Object Description: "DC Account Object"

             Value Object Attribute Name: msDFSR-ComputerReferenceBL

             Value Object Description: "SYSVOL FRS Member Object"

             Recommended Action: See Knowledge Base Article: Q312862


            [2] Problem: Missing Expected Value

             Base Object: CN=SERVER2,OU=Domain Controllers,DC=MOF,DC=ORG

             Base Object Description: "DC Account Object"

             Value Object Attribute Name: msDFSR-ComputerReferenceBL

             Value Object Description: "SYSVOL FRS Member Object"

             Recommended Action: See Knowledge Base Article: Q312862


            LDAP Error 0x20 (32) - No Such Object.
         ......................... SERVER2 failed test

         VerifyEnterpriseReferences

      Starting test: VerifyReferences

         The system object reference (serverReference)

         CN=SERVER2,OU=Domain Controllers,DC=MOF,DC=ORG and backlink on

         CN=SERVER2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=MOF,DC=ORG

         are correct.
         The system object reference (serverReferenceBL)

         CN=SERVER2,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=MOF,DC=ORG

         and backlink on

         CN=NTDS Settings,CN=SERVER2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=MOF,DC=ORG

         are correct.
         The system object reference (frsComputerReferenceBL)

         CN=SERVER2,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=MOF,DC=ORG

         and backlink on CN=SERVER2,OU=Domain Controllers,DC=MOF,DC=ORG are

         correct.
         ......................... SERVER2 passed test VerifyReferences

      Starting test: VerifyReplicas

         This NC (DC=DomainDnsZones,DC=MOF,DC=ORG) is supposed to be replicated

         to this server, but has not been replicated yet. This could be because

         the replica set changes haven't replicated here yet.  If this problem

         persists, check replication of the Configuration Partition to this

         server.
         This NC (DC=ForestDnsZones,DC=MOF,DC=ORG) is supposed to be replicated

         to this server, but has not been replicated yet. This could be because

         the replica set changes haven't replicated here yet.  If this problem

         persists, check replication of the Configuration Partition to this

         server.
         ......................... SERVER2 failed test VerifyReplicas

 Summary of DNS test results:

         
                                            Auth Basc Forw Del  Dyn  RReg Ext
            _________________________________________________________________
            Domain: MOF.ORG

               Server1                      PASS PASS PASS PASS WARN PASS n/a  
               Server2                      PASS PASS PASS PASS WARN PASS n/a 

                          

Viewing all articles
Browse latest Browse all 5877

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>