The error was: DNS name does not exist server 2022
In this article, we’ll take a look at why it’s not possible to join a new computer to the Active Directory domain with an error Active Directory Domain Controller could not be contacted. Show
Active Directory Domain Controller Could Not Be Contacted Error: What Does It Looks Like?A user or an administrator tries to join a new Windows workstation or server to the domain. To do this, open the System Properties on the workstation, and press Change settings > Change. Enter a new computer name, and select that this computer should be a member of a specified domain. Enter your AD domain FQDN name. After clicking on the OK button, you may receive an error:
How to Fix AD Domain Controller Could Not Be Connected Error?Here are some basic steps that should help you fix the domain controller connection error:
Let’s look at each of these steps in more detail. Check the IP Settings and DNS Settings on Your ComputerMost often, this problem is related to the wrong IP or DNS settings on your computer. Check IP AddressFirst, check if your computer has the correct IP address on the primary network interface. The IP address can be obtained from a DHCP server, or manually specified in the network adapter settings. You can view the current network settings of the computer using the command: ipconfig /all Make sure your computer’s IP address matches the network it’s on. Try to manually set a static IP address, or vice versa, get the correct address from the DHCP server (select Obtain IP address automatically in the properties of your network adapter). Check DNS Client SettingsMake sure your network adapter’s IP settings are set to your internal DNS servers. You can display the current DNS servers for your adapter using PowerShell: DnsClientServerAddress If the DNS server address is incorrect, change it manually or get settings from DHCP. Make sure the DNS Client service is running using Get-Service cmdlet: Get-Service dnscache Open the hosts file (C:\Windows\System32\Drivers\etc\hosts) on the computer using notepad.exe or another text editor, and make sure there are no entries for your domain or domain controller names. If such entries exist, delete them. You can display the contents of the hosts file with the command: get-content C:\Windows\System32\Drivers\etc\hosts Then clear the DNS cache, and restart the service from the elevated command prompt: ipconfig /flushdns net stop dnscache && net start dnscache Check if your computer can resolve the domain name to the correct IP address of the domain controller. Use the Resolve-DNSName cmdlet with the FQDN of your domain to which you are trying to join your workstation: Resolve-DNSName theitbros.com The command should return one or more records of DNS servers. Verify the Domain Controller ConnectivityNext, check if the domain controller is accessible from the client. Open a command prompt, and run the following commands: ping your_domain_name.com And: tracert your_domain_name.com Make sure your domain controller is responding and reachable.
If the DC is reachable, try to add the received IP address as a DNS server in the Advanced TCP/IP settings of your network connection.
Check If the Domain Controller Connections Aren’t Blocked By the FirewallVerify if the access to the DNS service on the domain controller is not blocked by firewalls. The easiest way to check the availability of port 53 on a DC is to use PowerShell: Test-Netconnection 192.168.1.11 -port 53 In our example, TcpTestSucceeded: True means that the DNS service on the DC is accessible. Also, make sure the computer can contact the DNS server that hosts the DNS zone or can resolve DNS names in that domain. Make sure the correct DNS server is configured on this client as preferred and the client is connected to this server. Confirm you can find a domain and access the domain controller from the computer using the command: nltest /dsgetdc:theitbros.com If your computer successfully discovered the domain and domain controller, the command should return information about the domain, AD site, and services running on the DC: DC: \\DC01.theitbros.com Address: \\192.168.1.15 Dom Guid: 4216f343-2949-21c3-8caa-6d7cbcdb1690 Dom Name: theitbros.com Forest Name: theitbros.com Dc Site Name: NY Our Site Name: NY Flags: PDC GC DS LDAP KDC TIMESERV GTIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE FULL_SECRET WS The command completed successfully.
Also, try to temporarily disable the built-in Windows Firewall, and all third-party applications with antivirus/firewalls modules (Symantec, MacAfee, Windows Defender, etc.), that can block network ports to access the domain controller. After disabling the firewalls, try to join the computer to the domain. Here is the minimum list of network protocols, ports, and services that must not be blocked in firewalls between a client and a domain controller to successfully join a device to the Active Directory domain:
Check the DNS SRV Records on the Domain ControllerCheck DNS Records on your DCIf the above method didn’t help, check if in the DNS zone of your domain controller there is an SRV record of the location of the DC. Open an elevated Command prompt, and run the following commands: nslookup set type=all _ldap._tcp.dc.msdcs.your_domain_name.com Verify if the specified DNS server has an SRV record in the following form: _ldap._tcp.dc._msdcs.your_domain_name.com SRV service location: If the specified SRV record is missing, it means your computer is configured to use a DNS server that does not have a correct SRV record with the location of the domain controller. Update/Re-Register DNS SRV Records on DCIf you can’t change the DNS settings on your computer, you can manually add two records (SRV and A) to your existing DNS server which help you to resolve the domain controller’s IP address:
Restart the Netlogon service on the domain controller with the command: net stop netlogon && net start netlogon (or simply try to reboot the DC) On startup, it will try to register the necessary SRV records on the DNS server. Also, you can re-register domain controller DNS records using the command: ipconfig /registerdns Wait for a while for the records to appear in DNS and replicate across the domain. Also, make sure the dynamic updates are allowed in your Windows DNS zone settings. Check the Domain Controller Health Perform a health check on your domain controllers and replication according to the following guides:
It is also recommended to verify if the SYSVOL and NETLOGON network shared folders are created and accessible on the domain controller (run the net share command on the closest DC). If the SYSVOL and NETLOGON directories are missing in the shares list:
And check if the directory DCName SYSVOL appears and is accessible on the problem DC. Troubleshooting Error “an Active Directory Domain Controller Could not be Contacted”If none of the above methods helped you to fix the problem, you need to move to more advanced troubleshooting. Note that the Details button is available in the error message. Click the Details button for more information about the error. In most cases, there you will see an error “DNS name does not exist” or one of the following error codes 0x0000232B RCODE_NAME_ERROR, 0x0000267C DNS_ERROR_NO_DNS_SERVER, and 0x00002746 WSAECONNRESET). For example:
Open the text file C:\windows\debug\dcdiag.txt on the user’s computer. Carefully study the latest errors in this file. Perhaps they will point you in the right direction. Most often, you can face such errors in the dcdiag.txt file:
Sometimes, in the Netsetup.log file, you can find useful information about errors in joining a computer to an Active Directory domain. It is Windows clients log the details of the domain join operation. This log can be found here %windir%\debug\Netsetup.log. Carefully examine the errors in the Netsetup.log file, they may help you in finding the problem of not being able to connect to the Active Directory domain. The most typical errors are:
I enjoy technology and developing websites. Since 2012 I'm running a few of my own websites, and share useful content on gadgets, PC administration and website promotion. How do you fix DNS name does not exist?To resolve the issue:. Navigate within the User Interface to Start > My Computer > Properties.. In the Windows Activation section, click Change Product Key.. Enter the new Multiple Activation Key (MAK).. Select Activate Windows for the newly entered product key. ... . Go to Start > All Programs > Accessories.. What does it mean the DNS name does not exist?This error message simply means your computer was unable to find the Active Directory Domain Controller, so you need to tell your computer where to find the DNS server.
|