none
dns not working properly

    Question

  • i have a server 2008 r2. i joind my vista laptop to the domain but the gruop policy is not deployed to the laptop and i think it is cause of dns not configured propoerly. this is my dcdiag result.

    somebody please help

    D:\Users\Administrator.SAMMY>dcdiag

    Directory Server Diagnosis

    Performing initial setup:
       Trying to find home server...
       Home Server = sammy
       * Identified AD Forest.
       Done gathering initial info.

    Doing initial required tests

       Testing server: Default-First-Site-Name\SAMMY
          Starting test: Connectivity
             The host e8749bc1-dccf-4cab-ae38-00bf3c2fdd06._msdcs.home.first 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.
             ......................... SAMMY failed test Connectivity

    Doing primary tests

       Testing server: Default-First-Site-Name\SAMMY
          Skipping all tests, because server SAMMY 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 : home
          Starting test: CheckSDRefDom
             ......................... home passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... home passed test CrossRefValidation

       Running enterprise tests on : home.first
          Starting test: LocatorCheck
             ......................... home.first passed test LocatorCheck
          Starting test: Intersite
             ......................... home.first passed test Intersite

    Wednesday, October 17, 2012 1:16 PM

Answers

  • Doing initial required tests

       Testing server: Default-First-Site-Name\SAMMY
          Starting test: Connectivity
             The host e8749bc1-dccf-4cab-ae38-00bf3c2fdd06._msdcs.home.first 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.
             ......................... SAMMY failed test Connectivity

    Yes, you already have a DNS resolution issue.

    I would recommend the following:

    • Make sure that DCs you have are using a single IP address and only one NIC card is enabled for them (all other NICs should disabled)
    • Choose a healthy DC / DNS server and make each DC points to it as primary DNS server
    • Make each DC / DNS server points to its private IP address as secondary one
    • Configure public DNS servers as forwarders and not in IP settings of DCs

    Once done, run ipconfig /registerdns and restart netlogon on each DC you have.

    For client computers, make them point to internal DC / DNS servers as primary and secondary DNS servers.

    Once done, you can use dcdiag and repadmin to troubleshoot AD replication.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer



    Wednesday, October 17, 2012 7:12 PM
  • i only have one NIC and ip4 address is 10.10.1.70 with 255.0.0.0 subnet. ip6 disabled

    No. This is not supported by Microsoft. IPv6 should be enabled. Just make sure that ::1 is not set as DNS server in IPv6.

    Please run ipconfig /registerdns and restart netlogon service on the DC.

    Also, please make sure that you have the following AD zones which should be primary ones (Better if they integrated to AD) and accepting updates:

      • domain.com
      • _msdcs.domain.com


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    Thursday, October 18, 2012 11:26 AM

All replies

  • Doing initial required tests

       Testing server: Default-First-Site-Name\SAMMY
          Starting test: Connectivity
             The host e8749bc1-dccf-4cab-ae38-00bf3c2fdd06._msdcs.home.first 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.
             ......................... SAMMY failed test Connectivity

    Yes, you already have a DNS resolution issue.

    I would recommend the following:

    • Make sure that DCs you have are using a single IP address and only one NIC card is enabled for them (all other NICs should disabled)
    • Choose a healthy DC / DNS server and make each DC points to it as primary DNS server
    • Make each DC / DNS server points to its private IP address as secondary one
    • Configure public DNS servers as forwarders and not in IP settings of DCs

    Once done, run ipconfig /registerdns and restart netlogon on each DC you have.

    For client computers, make them point to internal DC / DNS servers as primary and secondary DNS servers.

    Once done, you can use dcdiag and repadmin to troubleshoot AD replication.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer



    Wednesday, October 17, 2012 7:12 PM
  • hi thanks for reply

    i am very new to server 2008. can please tell in bit more detail. i will be really great-full. i am trying to tech myself to get a job. here is some more info.

    i only have one NIC and ip4 address is 10.10.1.70 with 255.0.0.0 subnet. ip6 disabled

    my DC, DNS and DHCP are on the same machine so in dns points to 10.10.1.70 alternate dns is empty

    there is only on vista machine connected to domain. but i am not able to deploy group policy. cannot run gpupdate from vista but runs all good on server.

    i can ping both ways.

    can tell me more about  how to configure forwarders. here is my ipconfig output from server2008

    D:\Users\Administrator.SAMMY>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : sammy
       Primary Dns Suffix  . . . . . . . : home.first
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : home.first

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) 82566DM-2 Gigabit Network Connec
    tion
       Physical Address. . . . . . . . . : 00-21-70-3E-B1-A0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 10.10.1.70(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.0.0.0
       Default Gateway . . . . . . . . . :
       DNS Servers . . . . . . . . . . . : 10.10.1.70
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{495586DB-FC30-4873-86B9-E4C9B25AB5E9}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 11:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    i named it sammy.first when created forest not sammy.first.com i hope thats not a problem

    here is how my dc looks like

    here is ipconfig from my vista client. which is connected to server through lan cable not wireless

    C:\Users\Krithika>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Krithika-PC
       Primary Dns Suffix  . . . . . . . : home.first
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : home.first
                                           Home

    Wireless LAN adapter Wireless Network Connection:

       Connection-specific DNS Suffix  . : Home
       Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Con
    nection
       Physical Address. . . . . . . . . : 00-1B-77-C1-F0-AD
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::50a5:cafa:e20a:ef66%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.6(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Friday, October 19, 2012 2:24:06 AM
       Lease Expires . . . . . . . . . . : Saturday, October 20, 2012 7:08:47 PM
       Default Gateway . . . . . . . . . : 192.168.1.1
       DHCP Server . . . . . . . . . . . : 192.168.1.1
       DHCPv6 IAID . . . . . . . . . . . : 184556407
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-77-DC-38-00-1A-A0-FD-FA-EE

       DNS Servers . . . . . . . . . . . : 192.168.1.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : home.first
       Description . . . . . . . . . . . : Broadcom NetLink (TM) Fast Ethernet
       Physical Address. . . . . . . . . : 00-1A-A0-FD-FA-EE
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 10.10.1.80(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.0.0.0
       Lease Obtained. . . . . . . . . . : Friday, October 19, 2012 7:16:13 PM
       Lease Expires . . . . . . . . . . : Saturday, October 27, 2012 7:16:13 PM
       Default Gateway . . . . . . . . . :
       DHCP Server . . . . . . . . . . . : 10.10.1.70
       DNS Servers . . . . . . . . . . . : 10.10.1.70
       Primary WINS Server . . . . . . . : 192.168.0.8
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Local Area Connection* 6:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : home.first
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 7:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : Home
       Description . . . . . . . . . . . : isatap.Home
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Thursday, October 18, 2012 9:37 AM
  • i only have one NIC and ip4 address is 10.10.1.70 with 255.0.0.0 subnet. ip6 disabled

    No. This is not supported by Microsoft. IPv6 should be enabled. Just make sure that ::1 is not set as DNS server in IPv6.

    Please run ipconfig /registerdns and restart netlogon service on the DC.

    Also, please make sure that you have the following AD zones which should be primary ones (Better if they integrated to AD) and accepting updates:

      • domain.com
      • _msdcs.domain.com


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    Thursday, October 18, 2012 11:26 AM