<div>
Hi, 
 
Does this server Ping neighbor servers or workstations? Does it have internet? 
Did the domain controller and dns work before? 
What has changed? 
 
If it did not work before, what can be found in event logging after a fresh boot? 
 
Cheers
</div>

<div>
&gt; Also the server has Red X on the network Icon 
 
this issue should be addressed first otherwise nothing can troubleshoot further. 
 
is it a VM or physical machine?
</div>

<div>
Nothing has changed, It can ping the workstation. There is also internet access on the server. this is not a VM, it is a physical machine
</div>

<div>
Ok, Windows sometimes Isnt sure if its network is functioning or not. 
 
Did you run dcdiag in elevated prompt? 
 
In server manager -&gt; dns, are there errors shown?
</div>

<div>
There is no such errors in server manager &gt;&nbsp;dns. 
 
Just ran the dcdiag in elevated prompt 
 
C:\Windows\system32&gt;dcdiag.exe 
 
Directory Server Diagnosis 
 
Performing initial setup: 
&nbsp; &nbsp;Trying to find home server... 
&nbsp; &nbsp;Home Server = SERVER 
&nbsp; &nbsp;* Identified AD Forest. 
&nbsp; &nbsp;Done gathering initial info. 
 
Doing initial required tests 
 
&nbsp; &nbsp;Testing server: Default-First-Site-Name\SERVER 
&nbsp; &nbsp; &nbsp; Starting test: Connectivity 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... SERVER passed test Connectivity 
 
Doing primary tests 
 
&nbsp; &nbsp;Testing server: Default-First-Site-Name\SERVER 
&nbsp; &nbsp; &nbsp; Starting test: Advertising 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... SERVER passed test Advertising 
&nbsp; &nbsp; &nbsp; Starting test: FrsEvent 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... SERVER passed test FrsEvent 
&nbsp; &nbsp; &nbsp; Starting test: DFSREvent 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... SERVER passed test DFSREvent 
&nbsp; &nbsp; &nbsp; Starting test: SysVolCheck 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... SERVER passed test SysVolCheck 
&nbsp; &nbsp; &nbsp; Starting test: KccEvent 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... SERVER passed test KccEvent 
&nbsp; &nbsp; &nbsp; Starting test: KnowsOfRoleHolders 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... SERVER passed test KnowsOfRoleHolders 
&nbsp; &nbsp; &nbsp; Starting test: MachineAccount 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... SERVER passed test MachineAccount 
&nbsp; &nbsp; &nbsp; Starting test: NCSecDesc 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... SERVER passed test NCSecDesc 
&nbsp; &nbsp; &nbsp; Starting test: NetLogons 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... SERVER passed test NetLogons 
&nbsp; &nbsp; &nbsp; Starting test: ObjectsReplicated 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... SERVER passed test ObjectsReplicated 
&nbsp; &nbsp; &nbsp; Starting test: Replications 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... SERVER passed test Replications 
&nbsp; &nbsp; &nbsp; Starting test: RidManager 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... SERVER passed test RidManager 
&nbsp; &nbsp; &nbsp; Starting test: Services 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... SERVER passed test Services 
&nbsp; &nbsp; &nbsp; Starting test: SystemLog 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... SERVER passed test SystemLog 
&nbsp; &nbsp; &nbsp; Starting test: VerifyReferences 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... SERVER passed test VerifyReferences 
 
 
&nbsp; &nbsp;Running partition tests on : ForestDnsZones 
&nbsp; &nbsp; &nbsp; Starting test: CheckSDRefDom 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... ForestDnsZones passed test CheckSDRefDom 
&nbsp; &nbsp; &nbsp; Starting test: CrossRefValidation 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... ForestDnsZones passed test 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;CrossRefValidation 
 
&nbsp; &nbsp;Running partition tests on : DomainDnsZones 
&nbsp; &nbsp; &nbsp; Starting test: CheckSDRefDom 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... DomainDnsZones passed test CheckSDRefDom 
&nbsp; &nbsp; &nbsp; Starting test: CrossRefValidation 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... DomainDnsZones passed test 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;CrossRefValidation 
 
&nbsp; &nbsp;Running partition tests on : Schema 
&nbsp; &nbsp; &nbsp; Starting test: CheckSDRefDom 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... Schema passed test CheckSDRefDom 
&nbsp; &nbsp; &nbsp; Starting test: CrossRefValidation 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... Schema passed test CrossRefValidation 
 
&nbsp; &nbsp;Running partition tests on : Configuration 
&nbsp; &nbsp; &nbsp; Starting test: CheckSDRefDom 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... Configuration passed test CheckSDRefDom 
&nbsp; &nbsp; &nbsp; Starting test: CrossRefValidation 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... Configuration passed test CrossRefValidation 
 
&nbsp; &nbsp;Running partition tests on : syed 
&nbsp; &nbsp; &nbsp; Starting test: CheckSDRefDom 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... syed passed test CheckSDRefDom 
&nbsp; &nbsp; &nbsp; Starting test: CrossRefValidation 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... syed passed test CrossRefValidation 
 
&nbsp; &nbsp;Running enterprise tests on : syed.local 
&nbsp; &nbsp; &nbsp; Starting test: LocatorCheck 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... syed.local passed test LocatorCheck 
&nbsp; &nbsp; &nbsp; Starting test: Intersite 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... syed.local passed test Intersite
</div>

<div>
can you please post the IPCONFIG /ALL and ROUTE PRINT results?
</div>

<div>
C:\Windows\system32&gt;ipconfig /all 
 
Windows IP Configuration 
 
&nbsp; &nbsp;Host Name . . . . . . . . . . . . : SERVER 
&nbsp; &nbsp;Primary Dns Suffix &nbsp;. . . . . . . : syed.local 
&nbsp; &nbsp;Node Type . . . . . . . . . . . . : Hybrid 
&nbsp; &nbsp;IP Routing Enabled. . . . . . . . : Yes 
&nbsp; &nbsp;WINS Proxy Enabled. . . . . . . . : No 
&nbsp; &nbsp;DNS Suffix Search List. . . . . . : syed.local 
 
Ethernet adapter Local Area Connection: 
 
&nbsp; &nbsp;Connection-specific DNS Suffix &nbsp;. : 
&nbsp; &nbsp;Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connectio 
n 
&nbsp; &nbsp;Physical Address. . . . . . . . . : 
&nbsp; &nbsp;DHCP Enabled. . . . . . . . . . . : No 
&nbsp; &nbsp;Autoconfiguration Enabled . . . . : Yes 
&nbsp; &nbsp;IPv4 Address. . . . . . . . . . . : 192.168.1.10(Preferred) 
&nbsp; &nbsp;Subnet Mask . . . . . . . . . . . : 255.255.255.0 
&nbsp; &nbsp;Default Gateway . . . . . . . . . : 192.168.1.1 
&nbsp; &nbsp;DNS Servers . . . . . . . . . . . : 192.168.1.10 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;127.0.0.1 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;8.8.8.8 
&nbsp; &nbsp;NetBIOS over Tcpip. . . . . . . . : Enabled 
 
Tunnel adapter isatap.{7ADD410A-61E1-41B7-A5F5-0D0CCE72000D}: 
 
&nbsp; &nbsp;Media State . . . . . . . . . . . : Media disconnected 
&nbsp; &nbsp;Connection-specific DNS Suffix &nbsp;. : 
&nbsp; &nbsp;Description . . . . . . . . . . . : Microsoft ISATAP Adapter 
&nbsp; &nbsp;Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 
&nbsp; &nbsp;DHCP Enabled. . . . . . . . . . . : No 
&nbsp; &nbsp;Autoconfiguration Enabled . . . . : Yes 
 
Tunnel adapter Local Area Connection* 11: 
 
&nbsp; &nbsp;Media State . . . . . . . . . . . : Media disconnected 
&nbsp; &nbsp;Connection-specific DNS Suffix &nbsp;. : 
&nbsp; &nbsp;Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface 
&nbsp; &nbsp;Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 
&nbsp; &nbsp;DHCP Enabled. . . . . . . . . . . : No 
&nbsp; &nbsp;Autoconfiguration Enabled . . . . : Yes 
 
 
C:\Windows\system32&gt;route print -4 
=========================================================================== 
Interface List 
&nbsp;11...00 25 90 d4 1b 8a ......Intel(R) 82574L Gigabit Network Connection 
&nbsp; 1...........................Software Loopback Interface 1 
&nbsp;12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 
&nbsp;13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface 
=========================================================================== 
 
IPv4 Route Table 
=========================================================================== 
Active Routes: 
Network Destination &nbsp; &nbsp; &nbsp; &nbsp;Netmask &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Gateway &nbsp; &nbsp; &nbsp; Interface &nbsp;Metric 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0.0.0.0 &nbsp; &nbsp; &nbsp;192.168.1.1 &nbsp; &nbsp; 192.168.1.10 &nbsp; &nbsp;276 
&nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp;255.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; 127.255.255.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; &nbsp; &nbsp; 192.168.1.0 &nbsp; &nbsp;255.255.255.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;192.168.1.10 &nbsp; &nbsp;276 
&nbsp; &nbsp; &nbsp;192.168.1.10 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;192.168.1.10 &nbsp; &nbsp;276 
&nbsp; &nbsp; 192.168.1.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;192.168.1.10 &nbsp; &nbsp;276 
&nbsp; &nbsp; &nbsp; &nbsp; 224.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp;240.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; &nbsp; &nbsp; &nbsp; 224.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp;240.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;192.168.1.10 &nbsp; &nbsp;276 
&nbsp; 255.255.255.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp; &nbsp; 127.0.0.1 &nbsp; &nbsp;306 
&nbsp; 255.255.255.255 &nbsp;255.255.255.255 &nbsp; &nbsp; &nbsp; &nbsp; On-link &nbsp; &nbsp; &nbsp;192.168.1.10 &nbsp; &nbsp;276 
=========================================================================== 
Persistent Routes: 
&nbsp; Network Address &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Netmask &nbsp;Gateway Address &nbsp;Metric 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0.0.0.0 &nbsp; &nbsp; &nbsp;192.168.1.1 &nbsp;Default 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0.0.0.0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0.0.0.0 &nbsp; &nbsp; &nbsp;192.168.1.1 &nbsp;Default 
===========================================================================
</div>

<div>
So dcdiag has no errors in elevated prompt means no domain issues. 
No dns errors in server manager. 
 
What is the problem?
</div>

<div>
Log Name: &nbsp; &nbsp; &nbsp;DNS Server 
Source: &nbsp; &nbsp; &nbsp; &nbsp;Microsoft-Windows-DNS-Server-Service 
Date: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;4/5/2017 8:53:39 AM 
Event ID: &nbsp; &nbsp; &nbsp;5504 
Task Category: None 
Level: &nbsp; &nbsp; &nbsp; &nbsp; Information 
Keywords: &nbsp; &nbsp; &nbsp;Classic 
User: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;N/A 
Computer: &nbsp; &nbsp; &nbsp;SERVER.syed.local 
Description: 
The DNS server encountered an invalid domain name in a packet from 173.254.179.200. The packet will be rejected. The event data contains the DNS packet.
</div>

<div>
the IPCONFIG ALL and ROUTE PRINT results look good for me. is it the only DC on your LAN? 
 
&gt;&nbsp;There is also internet access on the server. 
 
is the server also accessible from the internet via the router at 192.168.1.1, by port forwarding enabled against the server? 
 
&gt;&nbsp;173.254.179.200 
 
it is an IP on the internet in California. is it an known IP or source for you or your business?
</div>

<div>
If your dns server is open to the internet/vpn i trust this is a branch office? 
 
If so, inspect the event data, are you suppose to answer to the domain requested?
</div>

<div>
No comment has been added to this question in more than 21 days, so it is now classified as abandoned. 
 
I have recommended this question be closed as follows: 
 
Accept: David Johnson CD MVP (<a href="https:#a42080852" rel="ugc">https:#a42080852</a>) 
 
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above. 
 
seth2740 
Experts-Exchange Cleanup Volunteer
</div>

<div>
to be honest, i don't think the accepted comment would help if the author does have his own internal DNS server in place. of course, the comment is suggested as it is a way to optimise the settings (not to fix the facing problem).
</div>

<div>
<div class="content wysiwyg-content">
It seems to be an issue with the DNS not registered with the server. 
 
Also the server has Red X on the network Icon, 
 
I ran Dc Diag.exe and it did this... 
 
C:\Users\htsuser4.SYED&gt;dcdiag.exe 
 
Directory Server Diagnosis 
 
Performing initial setup: 
&nbsp; &nbsp;Trying to find home server... 
&nbsp; &nbsp;Home Server = SERVER 
&nbsp; &nbsp;* Identified AD Forest. 
&nbsp; &nbsp;Done gathering initial info. 
 
Doing initial required tests 
 
&nbsp; &nbsp;Testing server: Default-First-Site-Name\SERVER 
&nbsp; &nbsp; &nbsp; Starting test: Connectivity 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;The host f8e87b26-40a5-44db-acd2-349596073ec2._msdcs.syed.local could 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;not be resolved to an IP address. Check the DNS server, DHCP, server 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;name, etc. 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Got error while checking LDAP and RPC connectivity. Please check your 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;firewall settings. 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... SERVER failed test Connectivity 
 
Doing primary tests 
 
&nbsp; &nbsp;Testing server: Default-First-Site-Name\SERVER 
&nbsp; &nbsp; &nbsp; Skipping all tests, because server SERVER is not responding to directory 
&nbsp; &nbsp; &nbsp; service requests. 
 
 
&nbsp; &nbsp;Running partition tests on : ForestDnsZones 
&nbsp; &nbsp; &nbsp; Starting test: CheckSDRefDom 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... ForestDnsZones passed test CheckSDRefDom 
&nbsp; &nbsp; &nbsp; Starting test: CrossRefValidation 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... ForestDnsZones passed test 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;CrossRefValidation 
 
&nbsp; &nbsp;Running partition tests on : DomainDnsZones 
&nbsp; &nbsp; &nbsp; Starting test: CheckSDRefDom 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... DomainDnsZones passed test CheckSDRefDom 
&nbsp; &nbsp; &nbsp; Starting test: CrossRefValidation 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... DomainDnsZones passed test 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;CrossRefValidation 
 
&nbsp; &nbsp;Running partition tests on : Schema 
&nbsp; &nbsp; &nbsp; Starting test: CheckSDRefDom 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... Schema passed test CheckSDRefDom 
&nbsp; &nbsp; &nbsp; Starting test: CrossRefValidation 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... Schema passed test CrossRefValidation 
 
&nbsp; &nbsp;Running partition tests on : Configuration 
&nbsp; &nbsp; &nbsp; Starting test: CheckSDRefDom 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... Configuration passed test CheckSDRefDom 
&nbsp; &nbsp; &nbsp; Starting test: CrossRefValidation 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... Configuration passed test CrossRefValidation 
 
&nbsp; &nbsp;Running partition tests on : syed 
&nbsp; &nbsp; &nbsp; Starting test: CheckSDRefDom 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... syed passed test CheckSDRefDom 
&nbsp; &nbsp; &nbsp; Starting test: CrossRefValidation 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... syed passed test CrossRefValidation 
 
&nbsp; &nbsp;Running enterprise tests on : syed.local 
&nbsp; &nbsp; &nbsp; Starting test: LocatorCheck 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... syed.local passed test LocatorCheck 
&nbsp; &nbsp; &nbsp; Starting test: Intersite 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;......................... syed.local passed test Intersite
</div>
</div>

It seems to be an issue with the DNS not registered with the server. 

Also the server has Red X on the network Icon,

I ran Dc Diag.exe and it did this...

C:\Users\htsuser4.SYED>dcdiag.exe

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = SERVER
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\SERVER
      Starting test: Connectivity
         The host f8e87b26-40a5-44db-acd2-349596073ec2._msdcs.syed.local could
         not be resolved to an IP address. Check the DNS server, DHCP, server
         name, etc.
         Got error while checking LDAP and RPC connectivity. Please check your
         firewall settings.
         ......................... SERVER failed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\SERVER
      Skipping all tests, because server SERVER is not responding to directory
      service requests.


   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 : syed
      Starting test: CheckSDRefDom
         ......................... syed passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... syed passed test CrossRefValidation

   Running enterprise tests on : syed.local
      Starting test: LocatorCheck
         ......................... syed.local passed test LocatorCheck
      Starting test: Intersite
         ......................... syed.local passed test Intersite

Connectivity Test failed because Could not confirm the identity of this serve

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.