none
On reboot DNS Fails to start

    Question

  • I'm at my wit's end here...appreciate any ideas or insight.

    This is a small office with a single Windows 2008 R2 Standard that is acting as the DNS server and Active Directory Domain Controller.

    The symptom is that after rebooting, DNS will not start. As a result, Active Directory Domain Services fails to start as well...and a cascade of failures such as DFS-R errors appear, etc.

    This Dell sever has two NICs but I have only of them enabled and I have disabled IPv6.

    > ipconfig /all


    Windows IP Configuration

       Host Name . . . . . . . . . . . . : SVR
       Primary Dns Suffix  . . . . . . . : corp.doctormorad.com
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : corp.doctormorad.com

    Ethernet adapter LAN Connection 1:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client)
       Physical Address. . . . . . . . . : A4-BA-DB-08-31-68
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.0.200(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.0.1
       DNS Servers . . . . . . . . . . . : 127.0.0.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    > dcdiag /v


    Directory Server Diagnosis


    Performing initial setup:

       Trying to find home server...

       * Verifying that the local machine SVR, is a Directory Server.
       Home Server = SVR

       * Connecting to directory service on server SVR.

       * Identified AD Forest.
       Collecting AD specific global data
       * Collecting site info.

       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=corp,DC=doctormorad,DC=com,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
       The previous call succeeded
       Iterating through the sites
       Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=corp,DC=doctormorad,DC=com
       Getting ISTG and options for the site
       * Identifying all servers.

       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=corp,DC=doctormorad,DC=com,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
       The previous call succeeded....
       The previous call succeeded
       Iterating through the list of servers
       Getting information for the server CN=NTDS Settings,CN=SVR,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=corp,DC=doctormorad,DC=com
       objectGuid obtained
       InvocationID obtained
       dnsHostname obtained
       site info obtained
       All the info for the server collected
       * Identifying all NC cross-refs.

       * Found 1 DC(s). Testing 1 of them.

       Done gathering initial info.


    Doing initial required tests

      
       Testing server: Default-First-Site-Name\SVR

          Starting test: Connectivity

             * Active Directory LDAP Services Check
             Determining IP4 connectivity
             * Active Directory RPC Services Check
             ......................... SVR passed test Connectivity



    Doing primary tests

      
       Testing server: Default-First-Site-Name\SVR

          Starting test: Advertising

             The DC SVR is advertising itself as a DC and having a DS.
             The DC SVR is advertising as an LDAP server
             The DC SVR is advertising as having a writeable directory
             The DC SVR is advertising as a Key Distribution Center
             The DC SVR is advertising as a time server
             The DS SVR is advertising as a GC.
             ......................... SVR passed test Advertising

          Test omitted by user request: CheckSecurityError

          Test omitted by user request: CutoffServers

          Starting test: FrsEvent

             * The File Replication Service Event log test
             Skip the test because the server is running DFSR.

             ......................... SVR passed test FrsEvent

          Starting test: DFSREvent

             The DFS Replication Event Log.
             There are warning or error events within the last 24 hours after the

             SYSVOL has been shared.  Failing SYSVOL replication problems may cause

             Group Policy problems.
             An error event occurred.  EventID: 0xC00004B2

                Time Generated: 08/20/2010   15:06:34

                Event String:

                The DFS Replication service failed to contact domain controller  to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.

                

                Additional Information:

                Error: 160 (One or more arguments are not correct.)

             An error event occurred.  EventID: 0xC00004B2

                Time Generated: 08/20/2010   16:08:10

                Event String:

                The DFS Replication service failed to contact domain controller  to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.

                

                Additional Information:

                Error: 160 (One or more arguments are not correct.)

             An error event occurred.  EventID: 0xC00004B2

                Time Generated: 08/20/2010   16:40:25

                Event String:

                The DFS Replication service failed to contact domain controller  to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.

                

                Additional Information:

                Error: 160 (One or more arguments are not correct.)

             An error event occurred.  EventID: 0xC00004B2

                Time Generated: 08/20/2010   16:46:01

                Event String:

                The DFS Replication service failed to contact domain controller  to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.

                

                Additional Information:

                Error: 160 (One or more arguments are not correct.)

             ......................... SVR failed test DFSREvent

          Starting test: SysVolCheck

             * The File Replication Service SYSVOL ready test
             File Replication Service's SYSVOL is ready
             ......................... SVR passed test SysVolCheck

          Starting test: KccEvent

             * The KCC Event log test
             Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
             ......................... SVR passed test KccEvent

          Starting test: KnowsOfRoleHolders

             Role Schema Owner = CN=NTDS Settings,CN=SVR,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=corp,DC=doctormorad,DC=com
             Role Domain Owner = CN=NTDS Settings,CN=SVR,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=corp,DC=doctormorad,DC=com
             Role PDC Owner = CN=NTDS Settings,CN=SVR,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=corp,DC=doctormorad,DC=com
             Role Rid Owner = CN=NTDS Settings,CN=SVR,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=corp,DC=doctormorad,DC=com
             Role Infrastructure Update Owner = CN=NTDS Settings,CN=SVR,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=corp,DC=doctormorad,DC=com
             ......................... SVR passed test KnowsOfRoleHolders

          Starting test: MachineAccount

             Checking machine account for DC SVR on DC SVR.
             * SPN found :LDAP/SVR.corp.doctormorad.com/corp.doctormorad.com
             * SPN found :LDAP/SVR.corp.doctormorad.com
             * SPN found :LDAP/SVR
             * SPN found :LDAP/SVR.corp.doctormorad.com/CORP
             * SPN found :LDAP/20db577e-1837-431d-b729-327d74b264f7._msdcs.corp.doctormorad.com
             * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/20db577e-1837-431d-b729-327d74b264f7/corp.doctormorad.com
             * SPN found :HOST/SVR.corp.doctormorad.com/corp.doctormorad.com
             * SPN found :HOST/SVR.corp.doctormorad.com
             * SPN found :HOST/SVR
             * SPN found :HOST/SVR.corp.doctormorad.com/CORP
             * SPN found :GC/SVR.corp.doctormorad.com/corp.doctormorad.com
             ......................... SVR passed test MachineAccount

          Starting test: NCSecDesc

             * Security Permissions check for all NC's on DC SVR.
             * Security Permissions Check for

               DC=ForestDnsZones,DC=corp,DC=doctormorad,DC=com
                (NDNC,Version 3)
             * Security Permissions Check for

               DC=DomainDnsZones,DC=corp,DC=doctormorad,DC=com
                (NDNC,Version 3)
             * Security Permissions Check for

               CN=Schema,CN=Configuration,DC=corp,DC=doctormorad,DC=com
                (Schema,Version 3)
             * Security Permissions Check for

               CN=Configuration,DC=corp,DC=doctormorad,DC=com
                (Configuration,Version 3)
             * Security Permissions Check for

               DC=corp,DC=doctormorad,DC=com
                (Domain,Version 3)
             ......................... SVR passed test NCSecDesc

          Starting test: NetLogons

             * Network Logons Privileges Check
             Verified share \\SVR\netlogon
             Verified share \\SVR\sysvol
             ......................... SVR passed test NetLogons

          Starting test: ObjectsReplicated

             SVR is in domain DC=corp,DC=doctormorad,DC=com
             Checking for CN=SVR,OU=Domain Controllers,DC=corp,DC=doctormorad,DC=com in domain DC=corp,DC=doctormorad,DC=com on 1 servers
                Object is up-to-date on all servers.
             Checking for CN=NTDS Settings,CN=SVR,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=corp,DC=doctormorad,DC=com in domain CN=Configuration,DC=corp,DC=doctormorad,DC=com on 1 servers
                Object is up-to-date on all servers.
             ......................... SVR passed test ObjectsReplicated

          Test omitted by user request: OutboundSecureChannels

          Starting test: Replications

             * Replications Check
             * Replication Latency Check
             ......................... SVR passed test Replications

          Starting test: RidManager

             * Available RID Pool for the Domain is 1600 to 1073741823
             * SVR.corp.doctormorad.com is the RID Master
             * DsBind with RID Master was successful
             * rIDAllocationPool is 1100 to 1599
             * rIDPreviousAllocationPool is 1100 to 1599
             * rIDNextRID: 1135
             ......................... SVR passed test RidManager

          Starting test: Services

             * Checking Service: EventSystem
             * Checking Service: RpcSs
             * Checking Service: NTDS
             * Checking Service: DnsCache
             * Checking Service: DFSR
             * Checking Service: IsmServ
                IsmServ Service is stopped on [SVR]

             * Checking Service: kdc
             * Checking Service: SamSs
             * Checking Service: LanmanServer
             * Checking Service: LanmanWorkstation
             * Checking Service: w32time
             * Checking Service: NETLOGON
             ......................... SVR failed test Services

          Starting test: SystemLog

             * The System Event log test
             An error event occurred.  EventID: 0xC004000B

                Time Generated: 08/20/2010   18:47:52

                Event String:

                The driver detected a controller error on \Device\Harddisk2\DR2.

             A warning event occurred.  EventID: 0x000003F6

                Time Generated: 08/20/2010   18:49:10

                Event String:

                Name resolution for the name www.microsoft.com timed out after none of the configured DNS servers responded.

             A warning event occurred.  EventID: 0x000003F6

                Time Generated: 08/20/2010   18:54:26

                Event String:

                Name resolution for the name www.erpalok.ru timed out after none of the configured DNS servers responded.

             A warning event occurred.  EventID: 0x000003F6

                Time Generated: 08/20/2010   19:00:17

                Event String:

                Name resolution for the name 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa timed out after none of the configured DNS servers responded.

             A warning event occurred.  EventID: 0x00001695

                Time Generated: 08/20/2010   19:23:39

                Event String:

                Dynamic registration or deletion of one or more DNS records associated with DNS domain 'corp.doctormorad.com.' failed.  These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition). 

               

                Possible causes of failure include: 

                - TCP/IP properties of the network connections of this computer contain wrong IP address(es) of the preferred and alternate DNS servers

                - Specified preferred and alternate DNS servers are not running

                - DNS server(s) primary for the records to be registered is not running

                - Preferred or alternate DNS servers are configured with wrong root hints

                - Parent DNS zone contains incorrect delegation to the child zone authoritative for the DNS records that failed registration 

               

                USER ACTION 

                Fix possible misconfiguration(s) specified above and initiate registration or deletion of the DNS records by running 'nltest.exe /dsregdns' from the command prompt on the domain controller or by restarting Net Logon service on the domain controller.

             A warning event occurred.  EventID: 0x00001695

                Time Generated: 08/20/2010   19:23:39

                Event String:

                Dynamic registration or deletion of one or more DNS records associated with DNS domain 'ForestDnsZones.corp.doctormorad.com.' failed.  These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition). 

               

                Possible causes of failure include: 

                - TCP/IP properties of the network connections of this computer contain wrong IP address(es) of the preferred and alternate DNS servers

                - Specified preferred and alternate DNS servers are not running

                - DNS server(s) primary for the records to be registered is not running

                - Preferred or alternate DNS servers are configured with wrong root hints

                - Parent DNS zone contains incorrect delegation to the child zone authoritative for the DNS records that failed registration 

               

                USER ACTION 

                Fix possible misconfiguration(s) specified above and initiate registration or deletion of the DNS records by running 'nltest.exe /dsregdns' from the command prompt on the domain controller or by restarting Net Logon service on the domain controller.

             A warning event occurred.  EventID: 0x00001695

                Time Generated: 08/20/2010   19:23:39

                Event String:

                Dynamic registration or deletion of one or more DNS records associated with DNS domain 'DomainDnsZones.corp.doctormorad.com.' failed.  These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition). 

               

                Possible causes of failure include: 

                - TCP/IP properties of the network connections of this computer contain wrong IP address(es) of the preferred and alternate DNS servers

                - Specified preferred and alternate DNS servers are not running

                - DNS server(s) primary for the records to be registered is not running

                - Preferred or alternate DNS servers are configured with wrong root hints

                - Parent DNS zone contains incorrect delegation to the child zone authoritative for the DNS records that failed registration 

               

                USER ACTION 

                Fix possible misconfiguration(s) specified above and initiate registration or deletion of the DNS records by running 'nltest.exe /dsregdns' from the command prompt on the domain controller or by restarting Net Logon service on the domain controller.

             ......................... SVR failed test SystemLog

          Test omitted by user request: Topology

          Test omitted by user request: VerifyEnterpriseReferences

          Starting test: VerifyReferences

             The system object reference (serverReference)

             CN=SVR,OU=Domain Controllers,DC=corp,DC=doctormorad,DC=com and

             backlink on

             CN=SVR,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=corp,DC=doctormorad,DC=com

             are correct.
             The system object reference (serverReferenceBL)

             CN=SVR,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=corp,DC=doctormorad,DC=com

             and backlink on

             CN=NTDS Settings,CN=SVR,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=corp,DC=doctormorad,DC=com

             are correct.
             The system object reference (msDFSR-ComputerReferenceBL)

             CN=SVR,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=corp,DC=doctormorad,DC=com

             and backlink on

             CN=SVR,OU=Domain Controllers,DC=corp,DC=doctormorad,DC=com are

             correct.
             ......................... SVR passed test VerifyReferences

          Test omitted by user request: VerifyReplicas

      
          Test omitted by user request: DNS

          Test omitted by user request: DNS

      
       Running partition tests on : ForestDnsZones

          Starting test: CheckSDRefDom

             ......................... ForestDnsZones passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... ForestDnsZones passed test

             CrossRefValidation

      
       Running partition tests on : DomainDnsZones

          Starting test: CheckSDRefDom

             ......................... DomainDnsZones passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... DomainDnsZones passed test

             CrossRefValidation

      
       Running partition tests on : Schema

          Starting test: CheckSDRefDom

             ......................... Schema passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... Schema passed test CrossRefValidation

      
       Running partition tests on : Configuration

          Starting test: CheckSDRefDom

             ......................... Configuration passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... Configuration passed test CrossRefValidation

      
       Running partition tests on : corp

          Starting test: CheckSDRefDom

             ......................... corp passed test CheckSDRefDom

          Starting test: CrossRefValidation

             ......................... corp passed test CrossRefValidation

      
       Running enterprise tests on : corp.doctormorad.com

          Test omitted by user request: DNS

          Test omitted by user request: DNS

          Starting test: LocatorCheck

             GC Name: \\SVR.corp.doctormorad.com

             Locator Flags: 0xe00033fd
             PDC Name: \\SVR.corp.doctormorad.com
             Locator Flags: 0xe00033fd
             Time Server Name: \\SVR.corp.doctormorad.com
             Locator Flags: 0xe00033fd
             Preferred Time Server Name: \\SVR.corp.doctormorad.com
             Locator Flags: 0xe00033fd
             KDC Name: \\SVR.corp.doctormorad.com
             Locator Flags: 0xe00033fd
             ......................... corp.doctormorad.com passed test

             LocatorCheck

          Starting test: Intersite

             Skipping site Default-First-Site-Name, this site is outside the scope

             provided by the command line arguments provided.
             ......................... corp.doctormorad.com passed test Intersite

    >nltest /dsregdns
    Flags: 0
    Connection Status = 0 0x0 NERR_Success
    The command completed successfully

     

    Any ideas or thoughts are much appreciated.

     

    Saturday, August 21, 2010 2:36 AM

All replies

  • Hi,

     

    When did the problem start? did you install the latest drivers for the NICs?

     

    Regards,

    Saturday, August 21, 2010 10:26 AM
  • Can you start it manually? What errors are you seeing in the Event Log?

    hth
    Marcin

    Saturday, August 21, 2010 11:43 AM
  • Some more background: I had previously attempted to install the domain using doctormorad.local but then changed my mind so I deleted the AD and DNS instances and re-ran dcpromo. The DNS not starting automatically on reboot started sometime after that - can't tell exactly when. For certain it continued to be auto-started but then stopped doing so.

    In attempting to resolve this, I noticed that there were still some "remnants" and references to doctormorad.local so, I went thru the registry and removed all doctormorad.local references. There were also a few DNS-related files in %SYSTEMROOT%\system32 referring to doctormorad.local, I removed those files. I also noticed that the Forward lookup zone (FLZ) for _msdcs.corp.doctormorad.com had not been created. So, I manually created that FLZ.

    I've updated the firmware as well as the drivers on the Broadcom NICs to the latest available ones from Dell. This is a brand new T610 server with two embedded NICs - only one of which is enabled.

    After a reboot, the DNS service doesn't automatically start but if I got to Server Manager, I can start it manually and then everything appears to be in working order.

    Regarding Events:

    If I carefully follow the startup sequence for the earliest event (via the SYSTEM log), the event log appears to show that the network subsystem is "not ready" when DNS needs to start.

    Key Events that appear in the log include the following:

    Log Name:      System
    Source:        Service Control Manager
    Date:          8/20/2010 4:45:25 PM
    Event ID:      7023
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SVR.corp.doctormorad.com
    Description:
    The DNS Server service terminated with the following error:
    The network is not present or not started.

    Log Name:      System
    Source:        Service Control Manager
    Date:          8/20/2010 4:45:27 PM
    Event ID:      7023
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SVR.corp.doctormorad.com
    Description:
    The Intersite Messaging service terminated with the following error:
    The specified server cannot perform the requested operation.


    Log Name:      File Replication Service
    Source:        NtFrs
    Date:          7/21/2010 5:49:22 PM
    Event ID:      13575
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SVR.corp.doctormorad.com
    Description:
    This domain controller has migrated to using the DFS Replication service to replicate the SYSVOL share. Use of the File Replication Service for replication of non-SYSVOL content sets has been deprecated and therefore, the service has been stopped. The DFS Replication service is recommended for replication of folders, the SYSVOL share on domain controllers and DFS link targets.


    Log Name:      DFS Replication
    Source:        DFSR
    Date:          8/20/2010 4:46:01 PM
    Event ID:      1202
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SVR.corp.doctormorad.com
    Description:
    The DFS Replication service failed to contact domain controller  to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.
     
    Additional Information:
    Error: 160 (One or more arguments are not correct.)

     

    Some of the events that I receive now even after a successful start is:

    Log Name:      DNS Server
    Source:        Microsoft-Windows-DNS-Server-

    Service
    Date:          8/20/2010 4:51:02 PM
    Event ID:      4010
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SVR.corp.doctormorad.com
    Description:
    The DNS server was unable to create a resource record for  20db577e-1837-431d-b729-327d74b264f7._msdcs.corp.doctormorad.com . in zone corp.doctormorad.com . The Active Directory definition of this resource record is corrupt or contains an invalid DNS name. The event data contains the error.


    but when I check the DNS entries, it is there...since this entry is created dynamically, I thought maybe there's something wrong with dyn updates and indeed, it fails the Dyn test...see below.

    Perhaps there are multiple issues here so I was trying to focus on resolving this one issue that dcdiag is showing, unable to pass the Dyn test:

    > dcdiag /v /test:dns /dnsdynamicupdate


    Directory Server Diagnosis

    Performing initial setup:

       Trying to find home server...

       * Verifying that the local machine SVR, is a Directory Server.
       Home Server = SVR

       * Connecting to directory service on server SVR.

       * Identified AD Forest.
       Collecting AD specific global data
       * Collecting site info.

       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=corp,DC=doctormorad,DC=com,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
       The previous call succeeded
       Iterating through the sites
       Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=corp,DC=doctormorad,DC=com
       Getting ISTG and options for the site
       * Identifying all servers.

       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=corp,DC=doctormorad,DC=com,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
       The previous call succeeded....
       The previous call succeeded
       Iterating through the list of servers
       Getting information for the server CN=NTDS Settings,CN=SVR,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=corp,DC=doctormorad,DC=com
       objectGuid obtained
       InvocationID obtained
       dnsHostname obtained
       site info obtained
       All the info for the server collected
       * Identifying all NC cross-refs.

       * Found 1 DC(s). Testing 1 of them.

       Done gathering initial info.

    Doing initial required tests
      
       Testing server: Default-First-Site-Name\SVR

          Starting test: Connectivity

             * Active Directory LDAP Services Check
             Determining IP4 connectivity
             * Active Directory RPC Services Check
             ......................... SVR passed test Connectivity

    Doing primary tests

       Testing server: Default-First-Site-Name\SVR

          Starting test: DNS
            
             DNS Tests are running and not hung. Please wait a few minutes...
             See DNS test in enterprise tests section for results
             ......................... SVR passed test DNS
      
       Running enterprise tests on : corp.doctormorad.com
          Starting test: DNS
             Test results for domain controllers:

                DC: SVR.corp.doctormorad.com
                Domain: corp.doctormorad.com         
                     
                   TEST: Authentication (Auth)
                      Authentication test: Successfully completed
                     
                   TEST: Basic (Basc)
                      The OS
                      Microsoft Windows Server 2008 R2 Standard  (Service Pack level: 0.0)
                      is supported.
                      NETLOGON service is running
                      kdc service is running
                      DNSCACHE service is running
                      DNS service is running
                      DC is a DNS server
                      Network adapters information:
                      Adapter
                      [00000007] Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client):                
                         MAC address is A4:BA:DB:08:31:68
                         IP Address is static
                         IP address: 192.168.0.200
                         DNS servers:
                            127.0.0.1 (SVR) [Valid]
                      The A host record(s) for this DC was found
                      The SOA record for the Active Directory zone was found
                      The Active Directory zone on this DC/DNS server was found primary
                      Root zone on this DC/DNS server was not found
                     
                   TEST: Dynamic update (Dyn)
                      Test record dcdiag-test-record added successfully in zone corp.doctormorad.com
                      Warning: Failed to delete the test record dcdiag-test-record in zone corp.doctormorad.com
                      [Error details: 9505 (Type: Win32 - Description: Unsecured DNS packet.)]
            
            Summary of test results for DNS servers used by the above domain controllers:
                DNS server: 192.168.0.200 (SVR)
                   All tests passed on this DNS server
                   Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered            
             Summary of DNS test results:
            
                                                Auth Basc Forw Del  Dyn  RReg Ext
                _________________________________________________________________
                Domain: corp.doctormorad.com

                   SVR                          PASS PASS n/a  n/a  WARN n/a  n/a 
            
             ......................... corp.doctormorad.com passed test DNS

     

    Again, thank you for all your help

    Saturday, August 21, 2010 3:20 PM
  • I'm having the same problem and found this:

    http://www.petri.co.il/forums/showthread.php?t=48711

     

    I haven't had time to restart the server yet, but if it worked for him, I'll give it a try.  HTH

    Tuesday, November 16, 2010 8:41 PM
  • Steve,

     

    Do you have your DNS pointing to itself as primary or another DC/DNS server as primary.  Try pointing it to another box as primary and restart...trying to avoid race condition issues.

    Thanks

    Mike


    http://adisfun.blogspot.com
    http://twitter.com/mekline
    Tuesday, November 16, 2010 9:01 PM
  • I do have DNS pointing to both itself, and another DC.  I will try your suggestion too.  Just waiting for a time to reboot.

    Tuesday, November 16, 2010 9:05 PM
  • forget the name resolution which is at later stage for which the dns api's need to get loaded from dns.exe.

    Make sure your service starts after boot up , bcoz SCM gets loaded during boot which is a database hosting all the services

    Tuesday, November 23, 2010 9:24 AM
  • Just FYI, neither changing the speed & duplex, or pointing to another primary worked.  After restart, the DNS service was still not running.
    Tuesday, November 30, 2010 2:13 PM