FIX: The Specified Domain Either Does Not Exist Or Could Not Be ...
Maybe your like
This tutorial contains instructions to resolve the following problem, when you try to join a Windows based computer to an existing domain: "The Specified Domain Either Does Not Exist or Could Not Be Contacted".
The error "The Specified Domain Either Does Not Exist or Could Not Be Contacted" commonly occurs due to invalid DNS settings on the workstation's side, because Active directory requires you to use domain DNS to work properly (and not router's address).
![]()
How to fix: Specified Domain Does Not Exist or Could Not Be Contacted.
Let's suppose that your Active Directory Domain Controller (and DNS Server) is a Windows Server 2016 machine and is responsible for the domain "wintips.local" and has the IP Address "192.168.1.10".
At this example, the IP and the Preferred DNS address on the Primary Domain Controller (Server 2016) must be the same, e.g.
| Primary Domain Controller (Server 2016) | |
| Computer Name: | Server2k16 |
| Domain Name: | WINTIPS.LOCAL |
| IP Address (Static): | 192.168.1.10 |
| Subnet Mask: | 255.255.255.0 |
| Default Gateway: | 192.168.1.1 |
| Preferred DNS Server: | 192.168.1.10 |
Method 1. Set the Preferred DNS Server Address to match the Domain Controller's IP Address (on Client Workstation)
To resolve the "Specified Domain Does Not Exist or Could Not Be Contacted" error, you have to set the Preferred DNS IP to point to Primary Domain Controller's IP address, on each client workstation that you want to join in the domain. To do that:
1. Open Network and Sharing Center. 2. Right click on Local Area Connection and click Properties. 3. Double click on Internet Protocol TCP/IPv4. 4. Change the Preferred DNS server address to match the Primary Domain Controller's IP Address (e.g. "192.168.1.10" in this example). 6. Click OK twice and close all windows.
![]()
7. Try to join the workstation in the Domain.
Method 2. Specify the WINS Server's IP Address on Client.
If your Active Directory Domain Controller acts also as a WINS server, then set the WINS IP address to point to WINS Server's (Primary Domain Controller's IP address),* on the client machine that you want to join to the Domain. To do that:
* Note: This method works even when the Primary Domain Controller does not act as a WINS Server.
1. Open Network and Sharing Center. 2. Right click on Local Area Connection and click Properties. 3. Double click on Internet Protocol TCP/IPv4.
4. Click the Advanced button.
![]()
5. At WINS tab, click Add.
![]()
6. Type at WINS Server's IP Address filed, the IP address of the WINS server (e.g. "192.168.1.10" in this example) and click Add.
![]()
7. Press OK three (3) times to apply changes and close all windows.
8. Try to join the machine in the Domain.
That’s it! Let me know if this guide has helped you by leaving your comment about your experience. Please like and share this guide to help others.
If this article was useful for you, please consider supporting us by making a donation. Even $1 can a make a huge difference for us in our effort to continue to help others while keeping this site free:
- Author
- Recent Posts
- How to Back up Windows Server or Windows 10/11 with Veeam Backup Agent for Free. - December 18, 2025
- FIX: We can't find a required component to run Teams. (Solved) - December 15, 2025
- How To Restore Active Directory From a Windows Server Backup. - December 11, 2025
Tag » Ad Dc Could Not Be Contacted Server 2016
-
Active Directory Domain Controllers Couldn't Be Contacted - Imanami
-
Un Contrôleur De Domaine Active Directory (AD DC) N'a Pas Pu être ...
-
Fix: Active Directory Domain Controller Could Not Be Contacted
-
Fix: An Active Directory Domain Controller For The Domain Could Not ...
-
Active Directory Domain Controller For The Domain Could Not Be ...
-
"An Active Directory Domain Controller Could Not Be Contacted ...
-
Fix Active Directory Domain Controller Could Not Be Contacted
-
Fix "An Active Directory Domain Controller For The Domain Could Not ...
-
Fix: An Active Directory Domain Controller Could Not Be Contacted
-
Fix: Active Directory Domain Controller Could Not Be Contacted
-
Fix: Active Directory Domain Controller Could Not Be Contacted ...
-
Domain Controller Configuration Error (The Server Is Not Operational ...
-
Domain Controller Is Not Functioning Correctly - Windows Server
-
An Active Directory Domain Controller For The Domain Could Not Be ...