Server 2016 Domain Join Error Code 0x0000267C Windows Server | Troubleshooting Issues on Domain Join

Server 2016 Domain Join Error Code 0x0000267C Windows Server | Troubleshooting Issues on Domain Join? Editing a host file can be dangerous, and it can be miss leading. This is the first lesson of this post.

We will see how to perform the domain join operation for Server 2016 and How to avoid Server 2016 Domain Join Error Code 0x0000267C. I was not able to join the server to the domain.

I tried with NetBIOS name of the domain and full FQDN without success. I was confident that the DNS server was configured correctly on the newly built server. The entire troubleshooting and Domain join processes are explained in the video here.

The DC server was not reachable from the newly built server because of firewall configurations on the local server. I disabled the firewall on the server, which resolved the reachability issue.

Patch My PC

The basic checks we need to perform before joining a server 2016 to domain are

  1. Ping DC server with IP
  2. Ping DC server with a short name
  3. Ping DC server with FQDN
  4. Remove the host file entries if there is an entry with the domain name or DC server name.
  5. Check the required Firewall ports are opened between the member server and DC server.
  6. Check the antivirus software (Symantec/MacAfee) is NOT blocking the communication.
Server 2016 Domain Join Error

I received the following is the domain join error on the server 2016 machine. An Active Directory Domain Controller (AD DC) for the domain “Intune.com” could not be contacted. Ensure that the domain name is typed correctly. If the name is correct, click details for troubleshooting information. I made sure that the domain name was correctly entered.

C:\Windows\Debug\dcdiag.txt is the log file that can provide more details when you have any issues with domain join. I checked the DCDIAG.log file, and it gave more information about the domain join issue.

Domain Join Error Details

An 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 "intune.com".
The error was: "No DNS servers configured for local system." 
(error code 0x0000267C DNS_ERROR_NO_DNS_SERVERS)
The query was for the SRV record for _ldap._tcp.dc._msdcs.intune.com

Server 2016 Domain Join Error NO DNS SERVER

Resolution

The domain name was correctly mentioned during the server 2016 domain join process. Also, the server can ping the domain and DC. But when I checked the host file of the local 2016 server, then there were some entries of domain name mapping. I deleted those entries from the host file.

Also, I checked the IPCONFIG information on the server and noticed that the DNS server IP was not configured. Rather DNS server IP was configured as gateway device IP. I removed the gateway IP and correctly configure the DNS server IP in the IPCONFIG utility. More details are available in the video below.

Adaptiva

Author

Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.