An attempt to resolve the DNS name of a domain controller in the domain being joined has failed
Hi i am having a lot of problems in joining a computer to a domain i just created, i have 2 different VMs in the same network, two W2K8 server one of them is an AD, DNS and DHCP server, the other one i just wanted to join it to the domain created in the AD server and i am getting this error, if i do a ipconfig /all ic an see its pointing to th eDNS server, what could be the problem?
December 30th, 2011 4:20pm

restart the netlogon service on the domain controller running dns on the computer you are trying to join to the domain make sure that it has dns assigned via dhcp or set one as static dns entry.
Free Windows Admin Tool Kit Click here and download it now
December 30th, 2011 4:47pm

Already did, its not working i have re created the AD, DHCP and DNS server like 3 times now, i do not understand, is there any specific configuration?
December 30th, 2011 5:20pm

What happens when you ping your server? (ping YourServer) What happens when you ping your domain? (ping Yourdomain.com) Did you create your primary zone? (Yourdomain.com) Make sure that your DNS entry and Default Gateway are correct. Make sure that they are on the same subnet. When you set domain on the computer that you need to join use FQDN. (Computer.YourDomain.com) There shouldn't be anything else that you need to do.
Free Windows Admin Tool Kit Click here and download it now
December 30th, 2011 5:47pm

From the same DC: What happens when you ping your server? It answers What happens when you ping your domain? It answers Did you create your primary zone? (Yourdomain.com) Yes i did Make sure that your DNS entry and Default Gateway are correct. They are correct Make sure that they are on the same subnet. They are! When you set domain on the computer that you need to join use FQDN. (Computer.YourDomain.com) If i use th FQDN it can not find it, if i only use the nomain wihtout the .com it works... I noticed something from the computer that i want to join if i ping the domain it does not answer, but the DC itself does, what am i missing?
December 30th, 2011 6:04pm

Restart your DNS service. Run "ipconfig /registerdns" on both computer and check if the "A" records are created in the DNS. The fact that is responding to "Domain" but not "Domain.com" makes me think you are getting some sort of broadcast response or WINS not DNS response. Try running nslookup from the new computer. nslookup DC.domain.com
Free Windows Admin Tool Kit Click here and download it now
December 30th, 2011 6:13pm

How do i check the A records? Another thing i am noticing is that in the server name its loosing the IPs i keep validating them everytime! This is an isolated enviroment so i dont think i am getting some broadcast, this is all happening in a single host...
December 30th, 2011 6:19pm

If you go to Admin Tools - DNS You should be able to see some "A" records for both of the servers. (under your DomainName zone)
Free Windows Admin Tool Kit Click here and download it now
December 30th, 2011 6:25pm

Hi i found out where the problem was, i was using an IP 169.254.0.X, dont know why but it was giving me problems, when i used a different IPs it worked
January 13th, 2012 5:11pm

169.254.. is APIPA range you can only see computers that are in the same subnet, you would usually get that when the computer is unable to reach DHCP server to obtain IP address automatically.
Free Windows Admin Tool Kit Click here and download it now
January 13th, 2012 5:17pm

Actually i was using that range for all my subnet... Any way i just defined another IP range and it works thanks!
January 14th, 2012 10:48am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics