none
First time setting up home network - cannot join domain! :(

    Question

  • I have setup Server 2012 R2 with AD, DNS and DHCP, but I cannot join domain from Win7 and Win10 clients. Could you please help me?

    DC Server - ipconfig /all

    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : GILIUS-DC01
       Primary Dns Suffix  . . . . . . . : training.local
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : training.local
    
    Ethernet adapter Ethernet:
    
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
       Physical Address. . . . . . . . . : F4-6D-04-50-55-B4
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.1.80(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.254
       DNS Servers . . . . . . . . . . . : 127.0.0.1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Tunnel adapter isatap.{98FB96A0-8EA0-4E14-8737-4095578EFEC6}:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Windows 10 client - ipconfig /all

    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : DESKTOP-QP5TPF3
       Primary Dns Suffix  . . . . . . . : 
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : home
    
    Ethernet adapter Ethernet:
    
       Connection-specific DNS Suffix  . : home
       Description . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connection
       Physical Address. . . . . . . . . : D4-BE-D9-3A-E9-96
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::50bc:6159:2a7d:9279%14(Preferred) 
       IPv4 Address. . . . . . . . . . . : 192.168.1.64(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : 19 May 2018 16:17:23
       Lease Expires . . . . . . . . . . : 20 May 2018 16:17:35
       Default Gateway . . . . . . . . . : 192.168.1.254
       DHCP Server . . . . . . . . . . . : 192.168.1.254
       DHCPv6 IAID . . . . . . . . . . . : 248823513
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-22-91-D4-49-D4-BE-D9-3A-E9-96
       DNS Servers . . . . . . . . . . . : 192.168.1.254
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Wireless LAN adapter WiFi:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6205
       Physical Address. . . . . . . . . : 8C-70-5A-6F-3A-BC
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    
    Wireless LAN adapter Local Area Connection* 2:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
       Physical Address. . . . . . . . . : 8C-70-5A-6F-3A-BD
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    
    Wireless LAN adapter Local Area Connection* 3:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
       Physical Address. . . . . . . . . : 8E-70-5A-6F-3A-BC
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    
    Ethernet adapter Bluetooth Network Connection:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
       Physical Address. . . . . . . . . : 9C-B7-0D-EE-20-C8
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    

    Windows 7 client - ipconfig /all

    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : gilius-PC
       Primary Dns Suffix  . . . . . . . : 
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : home
    
    Ethernet adapter Local Area Connection:
    
       Connection-specific DNS Suffix  . : home
       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
       Physical Address. . . . . . . . . : E0-D5-5E-4E-A6-26
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.1.155(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : 19 May 2018 11:25:04
       Lease Expires . . . . . . . . . . : 20 May 2018 14:48:11
       Default Gateway . . . . . . . . . : 192.168.1.254
       DHCP Server . . . . . . . . . . . : 192.168.1.254
       DNS Servers . . . . . . . . . . . : 192.168.1.254
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Tunnel adapter isatap.home:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : home
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    
    Tunnel adapter Teredo Tunneling Pseudo-Interface:
    
       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

    Windows 10 client - ping gilius-dc01

    Pinging GILIUS-DC01 [192.168.1.80] with 32 bytes of data:
    Reply from 192.168.1.80: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.80: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.80: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.80: bytes=32 time<1ms TTL=128
    
    Ping statistics for 192.168.1.80:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms

    Windows 10 client - attempting to join domain:

    [img]https://s9.postimg.cc/fcejhzp67/w101.png/img]

    Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you have received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt.
    
    The domain name "training" might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.
    
    If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.
    
    The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "training":
    
    The error was: "DNS name does not exist."
    (error code 0x0000232B RCODE_NAME_ERROR)
    
    The query was for the SRV record for _ldap._tcp.dc._msdcs.training
    
    Common causes of this error include the following:
    
    - The DNS SRV records required to locate an AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when an AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:
    
    192.168.1.254
    
    - One or more of the following zones do not include delegation to its child zone:
    
    training
    . (the root zone)

    [img]https://s9.postimg.cc/5ruwv4f9r/w102.png/img]

    Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you have received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt.
    
    The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "training.local":
    
    The error was: "DNS name does not exist."
    (error code 0x0000232B RCODE_NAME_ERROR)
    
    The query was for the SRV record for _ldap._tcp.dc._msdcs.training.local
    
    Common causes of this error include the following:
    
    - The DNS SRV records required to locate an AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when an AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:
    
    192.168.1.254
    
    - One or more of the following zones do not include delegation to its child zone:
    
    training.local
    local
    . (the root zone)

    Windows 7 client - attempting to join domain

    [img]https://s9.postimg.cc/vool7kivj/w71.jpg[/img]

    [img]https://s9.postimg.cc/gfyntswwv/w71b.jpg[/img]

    [img]https://s9.postimg.cc/fqfvhg433/w72.jpg/img]

    Note: This information is intended for a network administrator.  If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt.
    
    The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "training.local":
    
    The error was: "DNS name does not exist."
    (error code 0x0000232B RCODE_NAME_ERROR)
    
    The query was for the SRV record for _ldap._tcp.dc._msdcs.training.local
    
    Common causes of this error include the following:
    
    - The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:
    
    192.168.1.254
    
    - One or more of the following zones do not include delegation to its child zone:
    
    training.local
    local
    . (the root zone)
    Saturday, May 19, 2018 4:43 PM

Answers

  • OK that worked - I can now join domain:

    1) Install AD (takes care of DNS)

    2) Install DHCP

    The only options I needed to add manually were: static IP, reverse lookup zone, and DNS suffix

    So, again the problem was:

    1) Install DNS + setup forward & reverse zones, DNS suffix, etc.

    2) Install AD + DHCP

    Resulted in not being able to join the domain!

    The only other problem is that after uninstalling all features and roles, my taskbar settings disappeared and need to be put back again.

    • Marked as answer by gilius2k15 Monday, May 21, 2018 8:24 PM
    Monday, May 21, 2018 8:24 PM

All replies

  • Hi Dave, I have the loopback address listed already.

    Why do the clients need static IP? I never had to set clients with static before when joining a domain.

    How to setup the router? I got BT Home Hub 5, but why do I never see this stage mentioned in any guides about Windows Server network setup, including on youtube videos?




    • Edited by gilius2k15 Saturday, May 19, 2018 5:03 PM
    Saturday, May 19, 2018 5:02 PM
  • How about if I put a hardware firewall in-between my router and switch? Could I add the DNS server in the firewall instead of changing my router?
    Saturday, May 19, 2018 5:19 PM
  • Another question: since the public DNS has no knowledge of my AD domain, how was I able to ping the DC host-name from a client?

    Pinging GILIUS-DC01 [192.168.1.80] with 32 bytes of data:
    Reply from 192.168.1.80: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.80: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.80: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.80: bytes=32 time<1ms TTL=128
    
    Ping statistics for 192.168.1.80:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0m
    Saturday, May 19, 2018 5:27 PM
  • Still not joining even after assigning a DNS server in the IP4 settings:

    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : gilius-PC
       Primary Dns Suffix  . . . . . . . : 
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : home
    
    Ethernet adapter Local Area Connection:
    
       Connection-specific DNS Suffix  . : home
       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
       Physical Address. . . . . . . . . : E0-D5-5E-4E-A6-26
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.1.155(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : 19 May 2018 18:44:59
       Lease Expires . . . . . . . . . . : 20 May 2018 18:44:58
       Default Gateway . . . . . . . . . : 192.168.1.254
       DHCP Server . . . . . . . . . . . : 192.168.1.254
       DNS Servers . . . . . . . . . . . : 192.168.1.80
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Tunnel adapter isatap.home:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : home
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    
    Tunnel adapter Teredo Tunneling Pseudo-Interface:
    
       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
    

    https://s9.postimg.cc/pvj4kwwnj/dns.jpg

    Saturday, May 19, 2018 5:55 PM
  • Hi gilius2k15,

    First welcome to the TechNet forums!

    - Make sure that the DNS services on the DC are running.
    -
    Perform a 'ipconfig /flush' on the clients/DC.
    - Please disable IPv6 on the NICs and try again.
    - Disable Windows Firewall on DC/client for testing purpose
    -
    What is the output of nslookup from the clients/DC?

    nslookup GILIUS-DC01

    Router DHCP server? (not a good idea)
    If you router is the DHCP server it will give your clients also DNS IP-address. In the properties of your NIC on the client you can change the order of use for DNS servers.

    1. Open the properties of the NIC on your Client.
    2. Go to IPv4.
    3. Go to the 'DNS' tab.
    4. Add here the IP-address of the DC, and make sure to set this to the top:

    http://www.martinbuist.com/wp-content/uploads/2014/07/dns-add.jpg

    NOTE: I prefer to disable DHCP on your router and enable the DHCP on your Domain Controller.


    Cheers,

    Martien van Dijk

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Check my Blog: https://windowstechblog.nl

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.



    Saturday, May 19, 2018 6:24 PM
  • *Both DNS Client and Server services are running
    *I did an ipconfig /flushdns on both DC and client
    *Ip6 was already disabled
    *I disabled all tabs of the Windows Firewall on both DC and Client (for testing purposes)
    *DNS server is set in IP4 settings on Client.

    Unfortunately, still cannot join domain - same error messages. Attempts from both Win10 and Win7 behave exactly the same way as they did before. Also when the server was restarting I wasn't able to resolve websites till it came back on - proving the DNS server was set successfully in the IP4 settings.


    • Edited by gilius2k15 Saturday, May 19, 2018 6:39 PM
    Saturday, May 19, 2018 6:39 PM
  • I've uploaded the logs here:
    https://1drv.ms/f/s!AuHAhmh6-oJsgSUVd0VYu9v-EVIH

    Saturday, May 19, 2018 6:53 PM
  • DC: have changed DNS from 127.0.0.1 to 192.168.1.80, but it hasn't made any difference.

    Client: had changed DNS just to 192.168.1.80 - did not help - but now I have the router listed as a secondary DNS

    So I don't think the issue lies there. Perhaps the dcdiag will yield further clues?

    Saturday, May 19, 2018 7:08 PM
  • I don't really know what to do with that last article.

    So what is wrong with my DNS then? I simply added the 3 aforementioned features/roles, including DNS, and I had setup a forwarding zone and reverse lookup zone. How to fix? Do I need to reinstall anything? Will I get the same problem with Server 2008 or Server 2016?

    Saturday, May 19, 2018 7:17 PM
  • Thanks for sharing the results. In the dcdiag.log there is a record that says: Name resolution is not functional. That can be the cause that the computers cannot join the domain, because the DNS-name training.local cannot be resolved.

    I think an ping to the domain training.local will fail from the clients? If so, the A-record for the domainname is missing.

    What's the output of this command from Powershell:

    $Zones = @(Get-DnsServerZone) 
    foreach ($Zone in $Zones) {
    	Write-Host "`n$($Zone.ZoneName)" -ForegroundColor "Green"
    	$Zone | Get-DnsServerResourceRecord
    }


    Cheers,

    Martien van Dijk

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Check my Blog: https://windowstechblog.nl

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.


    Saturday, May 19, 2018 7:35 PM
  • Right, I'm able to ping the DC hostname, but I cannot ping training.local - are we meant to be able to ping domainnames as opposed to the hostname/IP of a server?

    $Zones = @(Get-DnsServerZone) 
    foreach ($Zone in $Zones) {
    	Write-Host "`n$($Zone.ZoneName)" -ForegroundColor "Green"
    	$Zone | Get-DnsServerResourceRecord
    }

    If I've run this command correctly, the results were:

    0.in-addr.arpa DnsServerPrimaryZone

    1.168.192.in-addr.arpa DnsServerPrimaryZone

    127.in-addr.arpa DnsServerPrimaryZone

    255.in-addr.arpa DnsServerPrimaryZone

    training.local DnsServerPrimaryZone

    TrustAnchors DnsServerPrimaryZone

    dcdiag /fix hasn't helped

    • Edited by gilius2k15 Saturday, May 19, 2018 7:50 PM
    Saturday, May 19, 2018 7:47 PM
  • Ok. Yes, you need to can ping the domainname as a hostname.

    Now, i am wondering what your DNS-records are in the DNS-zone training.local.

    Please run this script with Powershell, and share me the contents of the training.local Primary Zone.

    $DNSServer = "192.168.1.80"
    $Zones = @(Get-DnsServerZone -ComputerName $DNSServer)
    ForEach ($Zone in $Zones) {
    	Write-Host "`n$($Zone.ZoneName)" -ForegroundColor "Green"
    	$Results = $Zone | Get-DnsServerResourceRecord -ComputerName $DNSServer
    	echo $Results > "$($Zone.ZoneName).txt"


    Cheers,

    Martien van Dijk

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Check my Blog: https://windowstechblog.nl

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Saturday, May 19, 2018 8:00 PM
  • 0.in-addr.arpa

    1.168.192.in-addr.arpa

    127.in-addr.arpa

    255.in-addr.arpa

    training.local

    TrustAnchors

    Unsure if outputted as desired - resulted in these logs:
    https://1drv.ms/f/s!AuHAhmh6-oJsgScIzCkbdE3UyV4y

    Saturday, May 19, 2018 8:17 PM
  • Thanks for sharing! You're missing some important DNS-records in zone training.local.

    Please add an A-record in Primary Zone training.local.

    1. Right click in zone training.local
    2. Choose for 'New Host (A or AAAA) ...
    3. Configure as below:

      Server 2012 R2 add dns record Windowstechblog.nl

    4. Click on 'Add Host'.
    5. Restart the DNS services
    6. Perform an ipconfig /flushdns and ipconfig /registerdns on the clients.

    Now you're able to ping the domainname from the clients.

    Further, the DNS is corrupt. the two records wich exists are not correct. I see gilius-dc01. as RecordData, this needs to bee gilius-dc01.training.local. So, the domain suffix is missing, and that's a problem.

    To repair the domain suffix, try to follow the steps on this page: Windows Server: DNS Suffix is Missing on Domain Controller Name Server Records



    Cheers,

    Martien van Dijk

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Check my Blog: https://windowstechblog.nl

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Saturday, May 19, 2018 8:28 PM
  • I've added the A record in the Forward lookup zone (= primary zone?)

    "I see gilius-dc01. as RecordData"

    Not sure where to see that in the GUI or how to correct it. I followed the guide and found under System properties Full computer name: gilius-dc01.training.local

    Clicking on More has:

    -Primary DNS suffix: training.local

    -NetBIOS name: gilius-dc01

    So the Full computer name seems to be comprised of those two because if I change the DNS suffix to gilius-dc01 then the full computer name becomes gilius-dc01.gilius-dc01.training.local, which is clearly incorrect.

    However, with just that A record change I'm now able to ping training.local from client!

    Unfortunately, I still cannot join the domain - same error messages as before. Strange.



    • Edited by gilius2k15 Saturday, May 19, 2018 9:38 PM
    Saturday, May 19, 2018 9:37 PM
  • I can't seem to ping training.local anymore now, but I could before. Nothing has changed - not sure what's happened.

    BTW, there is this warning on the server that I've had since the beginning:

    "The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed."


    • Edited by gilius2k15 Saturday, May 19, 2018 9:56 PM
    Saturday, May 19, 2018 9:56 PM
  • I flushed and registered client again and can now ping training.local again - yet it still cannot be contacted for adding to domain.
    • Edited by gilius2k15 Saturday, May 19, 2018 10:00 PM
    Saturday, May 19, 2018 10:00 PM
  • Goodmorning gilius2k15,

    I want to let you know that i am researching this error further for you now. It seems that still your DNS is missing some important records. We first need to fix this.

    Please check this post if your're missing some records please let me know: https://blogs.msdn.microsoft.com/servergeeks/2014/07/12/dns-records-that-are-required-for-proper-functionality-of-active-directory/

    Also run netdiag /fix and please share the outcome of this post through OneDrive.


    Cheers,

    Martien van Dijk

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Check my Blog: https://windowstechblog.nl

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.


    Monday, May 21, 2018 5:57 AM
  • Deepak,

    Please read first the reactions above before posting an reply. if you had done that, you would have known that comment does not add anything. Thanks!


    Cheers,

    Martien van Dijk

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Check my Blog: https://windowstechblog.nl

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Monday, May 21, 2018 7:54 AM
  • I am just checking if there is any update on this problem?

    Mayby it is worth considering to reinstall your Windows Server 2012 R2 server and reconfigure your AD/DNS. I think the environment where your problem is playing is a new environment and reinstalling Windows Server 2012 R2 is a faster solution.

    I would like to receive an update about the status.


    Cheers,

    Martien van Dijk

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Check my Blog: https://windowstechblog.nl

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Monday, May 21, 2018 6:06 PM
  • I spoke to somebody about this issue today, and he thinks that the AD feature/role did not get to finish adding the DNS entries that Martien is suggesting I manually add because I installed the DNS first before I installed AD, hence the warning message above ""The DNS server is waiting for Active Directory Domain Services...". 

    The step about adding DNS first came from this book, which failed to address the ISP/Router issue as well:

    https://www.amazon.co.uk/Microsoft-Windows-Server-Administration-Essentials/dp/1118016866/ref=sr_1_11?ie=UTF8&qid=1526928742&sr=8-11

    I will try uninstalling and reinstalling the 3 main features/roles. Modern Youtube videos suggest all 3 - DNS, AD, DHCP - can be installed simultaneously. However, the person I spoke to today said I should start with just AD (takes care of DNS automatically) and then finish with DHCP after that.

    If that fails then I will manually check through the link Martien provided.

    Monday, May 21, 2018 6:55 PM
  • OK that worked - I can now join domain:

    1) Install AD (takes care of DNS)

    2) Install DHCP

    The only options I needed to add manually were: static IP, reverse lookup zone, and DNS suffix

    So, again the problem was:

    1) Install DNS + setup forward & reverse zones, DNS suffix, etc.

    2) Install AD + DHCP

    Resulted in not being able to join the domain!

    The only other problem is that after uninstalling all features and roles, my taskbar settings disappeared and need to be put back again.

    • Marked as answer by gilius2k15 Monday, May 21, 2018 8:24 PM
    Monday, May 21, 2018 8:24 PM