DCDIAG error messages

This is the second domain controller in my network, I just did a dcpromo, but I see dcdiag reports problems.  The current DC is 172.31.1.9, which is also the only DNS server for 172.31.1.9.  Is ipconfig /registerdns enough to changes on the DCs or do I need to reboot the DCs?

seafile01 is 172.31.1.8

C:\Program Files\Support Tools>dcdiag
Domain Controller Diagnosis
Performing initial setup:
   Done gathering initial info.
Doing initial required tests
   Testing server: Default-First-Site-Name\SEAFILE01
      Starting test: Connectivity
         SEAFILE01's server GUID DNS name could not be resolved to an
         IP address.  Check the DNS server, DHCP, server name, etc
         Although the Guid DNS name
         (f97d215d-a810-4e40-a851-6e0431094234._msdcs.seabevad.local) couldn't
         be resolved, the server name (seafile01.seabevad.local) resolved to
         the IP address (172.31.1.8) and was pingable.  Check that the IP
         address is registered correctly with the DNS server.
         ......................... SEAFILE01 failed test Connectivity
Doing primary tests
   Testing server: Default-First-Site-Name\SEAFILE01
      Skipping all tests, because server SEAFILE01 is
      not responding to directory service requests
   Running enterprise tests on : seabevad.local
      Starting test: Intersite
         ......................... seabevad.local passed test Intersite
      Starting test: FsmoCheck
         Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
         A Global Catalog Server could not be located - All GC's are down.
         Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
         A Primary Domain Controller could not be located.
         The server holding the PDC role is down.
         Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
         A Time Server could not be located.
         The server holding the PDC role is down.
         Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
         A KDC could not be located - All the KDCs are down.
         ......................... seabevad.local failed test FsmoCheck

C:\Program Files\Support Tools>ipconfig /all
Windows IP Configuration
   Host Name . . . . . . . . . . . . : seafile01
   Primary Dns Suffix  . . . . . . . : seabevad.local
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : seabevad.local
Ethernet adapter Local Area Connection:
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
   Physical Address. . . . . . . . . : 00-0D-56-70-35-09
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 172.31.1.8
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 172.31.1.201
   DNS Servers . . . . . . . . . . . : 172.31.1.3
                                       172.31.1.9
jaaronsAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
mikeleebrlaConnect With a Mentor Commented:
one of your problems seems to be pretty obvious,,,  which computer is 172.31.1.3??? MS recommends DCs should be pointed to themselves for DNS resolution.  is this server 172.31.1.8 a DNS server? If not make it one and have it point to itself for DNS resolution....

FYI netdiag will not fix anything, it is just a diagnostics tool.
0
 
gjohnson99Commented:
Work run netdiag it may fix it
0
 
mikeleebrlaConnect With a Mentor Commented:
also,, do you just have one domain in your forrest?  if so go ahead and make both DCs Global Catalogs per this article:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;223346
0
 
WeHeConnect With a Mentor Commented:
like mike sayed, all members of a domain must point to a dynamically updateable dns, hosting it's zone.
normaly this is any DC in the domain.
configure seafile01 to host the seabevad.local zone in DNS. this zone should allready exist as an AD integrated one.
then point it's DNS settings in tcpip settings to itself (and only itself, no others)
restart "netlogon service" or reboot the server.
0
All Courses

From novice to tech pro — start learning today.