[Solved] An Attempt to Resolve the DNS name of a Domain Controller in the domain being joined has failed in Windows Server 2012

By | May 26, 2013

Recently I faced a Network issue while working on Windows server 2012 operating system.The error message was followed.

The following error occurred attempting to join the domain. 
An Attempt to Resolve the DNS name of a domain controller in the domain being joined has failed. Please verify the client is configured to reach a DNS server that can resolve DNS names in the target domain

I get this message when I was adding a PC to a newly created Windows server 2012 domain controller. I cross checked the DNS Server for Windows and found the reason for this problem.

How it comes

It comes when there is no Reverse lookup zone in the DNS server for windows. I checked my DNS server reverse lookup zone and found to be it was not configured.

When we are trying to add a client in the domain, we always specify the domain name, domain controller resolves name in to IP and vice versa. But here we have no reverse lookup zone and hence IP cannot be resolved to Name.

What is forward lookup zone and reverse lookup zone?

Forward Lookup Zone : Name to IP resolving
Reverse Lookup Zone : IP to Name resolving

(Our upcoming articles explain these concepts along with How to configure Reverse Look up Zone in Windows Server 2012? in deep, keep visiting SmartPCTricks)

In order to work a Domain Server properly we should configure reverse lookup zone, forward lookup zone automatically created at the time of DNS server installation.

Solve an Attempt to Resolve the DNS name of a domain controller issue is Windows Server 2012

Step 1: 
Open Start menu and go to DNS Manager

Step 2: 
Configure Reverse lookup zone under the reverse lookup zones area, then Refresh.

(Click on the Image to enlarge)
(I will explain How to set up DNS server later.)
Step 3:
Now you are able to add any PC to domain..! Try…

Keep reading SmartPCTricks for learning windows server 2012 online free.

11 thoughts on “[Solved] An Attempt to Resolve the DNS name of a Domain Controller in the domain being joined has failed in Windows Server 2012

  1. Scelo Dladla

    hi i have tried your solution to the error msg for login a client into a domain. bt im still getting the same error. can you perhaps give us a step by step guide on how to set it up from scratch

    Reply
    1. Admin

      Hi Scelo Dladla,
      This solution is the best way to resolve this issue. In my next article I will explain How to create DNS Reverse look up zone in Windows 2012 Server.

      Reply
    2. Eric Peterson

      I was going crazy trying to solve this problem. Everything worked great after I created the DNS Reverse Lookup Zone. Thanks for the tip.

      Reply
  2. Sreeranganath TV

    On windows 7 PC, An attempt to resolve the DNS name of a domain controller in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain. For information about network troubleshooting see windows help. The error occurred attempting to join the domain. Trying to add to windows 2008 R2 64 bit server thru windows 7 client but unable to connect and getting this error. Please provide solution.

    Reply
  3. Janis

    my solution was to enter primary DNS server ip adress on client network settings!

    Reply
  4. Sam

    This really works..solved my issue.. am able to get the machines under one domain..Thank you…

    Reply
  5. Shayan

    Change the network to static and type in these settings:

    IPv4 – 192.168.100.128

    Subnet Mask – 255.255.255.0

    Default Gateway – 192.168.100.10

    Preferred DNS Server – 192.168.100.5

    In system properties, you must field the Primary DNS suffix of this computer with your domain name sfi-wfc.com and than tick the box Change primary DNS suffix when domain membership changes.

    Restart Virtual Machine.

    Use Fully Qualified Domain Name (sfi-wfc.com) instead of NetBIOS name when joining a domain.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *