Can't get Windows 8.1 PC to resolve DNS name

We have a virtual domain with a DC and an RDS. Both those servers are 2012 R2. The RDS server joined the domain without any issues. The Windows 8 machine (also a vm) will not. I have tried everything that I and google have recommended and need more suggestions. I think at this point it would be simpler to field suggestions rather than trying to list everything I have tried already due to the sheer number.
Attached is a screen cap of the error.
A few of the basics I have tried...
Turned on and off firewall on both ends.
Pinged the dc successfully using the domain name and not ip
Flushed the dns cache
The primary dns in tcp/ip settings on the Win 8 vm is set to the ip of the dc

Any suggestions much appreciated.
domain-join-fail.JPG
Paul MontgomeryBusiness IT ProfessionalAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Justin YeungSenior Systems EngineerCommented:
1. ensure you can do resolution of the FQDN of the DC by using nslookup on the windows 8 machine
2. ping the fqdn of the DC
3. either using fqdn name on domain field when join domain (I see only a NetBIOS name on your error)
4. or add dns suffix to windows 8 machine with your domain FQDN name
0
*** Hopeleonie ***IT ManagerCommented:
It might be that SRV records are missing for DCs: https://support.microsoft.com/kb/816587

Use NSlookup as told:
http://social.technet.microsoft.com/wiki/contents/articles/29184.nslookup-for-beginners.aspx

Also make sure that your DCs are responding the recommended IP settings here: http://social.technet.microsoft.com/wiki/contents/articles/18513.active-directory-replication-issues-basic-troubleshooting-steps-single-ad-domain-in-a-single-ad-forest.aspx

If all of this does not help then you might want to temporary disable security software in use.
0
matrix8086Commented:
first of all: you should ping the IP of the DC, because the DNS in the TCP/IP settings contains IP address not other crazy stuffs !!! If that is working you can move on with more investigation
0
Introducing the "443 Security Simplified" Podcast

This new podcast puts you inside the minds of leading white-hat hackers and security researchers. Hosts Marc Laliberte and Corey Nachreiner turn complex security concepts into easily understood and actionable insights on the latest cyber security headlines and trends.

JohnBusiness Consultant (Owner)Commented:
Also, are you sure the Windows 8.1 virtual machine is Windows 8.1 Pro?   Windows 8.1 with no qualifier is Windows Home.
0
matrix8086Commented:
Correct: Windows home edition cannot be part of AD
0
Justin YeungSenior Systems EngineerCommented:
I don't think the "Domain" and "Network ID" option is available if you are using "Home" edition.
0
Paul MontgomeryBusiness IT ProfessionalAuthor Commented:
Thanks everyone. It is Windows 8.1 Pro. The domain is called pdmsource. When I do an nslookup I type pdmdc.pdmsource.local (fqdn). pdmdc is the server name, pdmsource is the domain name. The results are below...
nslookup.JPGIf I just type pdmsource.local I get...
nslookup2JPG.JPG
0
JohnBusiness Consultant (Owner)Commented:
Is 192.168.1.1 the address of your domain server?  If not, where does 192.168.1.1 come from in your environment?
0
Justin YeungSenior Systems EngineerCommented:
it looks like there isn't a correct A record for your DC IN DNS

do a upcoming /registers a on your DC
 And confirm resolution on the DC
0
Paul MontgomeryBusiness IT ProfessionalAuthor Commented:
192.168.1.1 is the correct IP of the domain server.
Justin I'm not sure what you are asking me to do as far as the command goes.
0
Justin YeungSenior Systems EngineerCommented:
on your domain controller

open command prompt

type in

ipconfig /registerdns
0
JohnBusiness Consultant (Owner)Commented:
Strange because the message says non-existent domain and so why would this true if the IP address is correct.

It does not seem like a Windows 8.1 Pro issue to me at this point.
0
Paul MontgomeryBusiness IT ProfessionalAuthor Commented:
Justin, I ran that and don't see any errors or warnings in the Event Viewer. Not sure if you wanted me to try to join that Win 8 VM again but I did with the same results.
John, I suspect it has something to do with the dns on the server as well. Something is more than likely incorrect in the DNS settings. I'm just not sure what I should be looking for. Here is a screen shot of the DNS. Not sure if this helps...
dnssettings.JPG
0
Justin YeungSenior Systems EngineerCommented:
There is no a record of your domain controller

What is the DNS settings on your DC?
0
JohnBusiness Consultant (Owner)Commented:
There is also no record of any workstations. Looking at client Server 2012 (Domain Controller) the first three items are the same, but then it goes on to list workstations. There is nothing there in your setup .
0
Justin YeungSenior Systems EngineerCommented:
It is normal that there isn't any workstation, since it doesn't has a part of DNS suffix or DHCP doesn't force the settings.

however NO A record of your DC is an issue, another word no one can find your DC with NAME.

confirm your DNS settings on your DC that is pointing to itself, then do ipconfig /registerdns.

you should then see an A record of your DC in your DNS.
0
Paul MontgomeryBusiness IT ProfessionalAuthor Commented:
John, no workstations have joined yet. This is the first. I do however have a RDS that is 2012 R2 that successfully joined as shown below...
demoserver.JPGJustin, it is pointing to itself and it was when I did the ipconfig /registerdns ...
tcpip.JPG
0
Justin YeungSenior Systems EngineerCommented:
how come you have pdmdc.local as a name server record?
isn't pdmdc is the name of DC? the name server record should be pdmdc.pdmsource.local

did you make any changes on DNS?
0
Paul MontgomeryBusiness IT ProfessionalAuthor Commented:
Yes pdmc is the name of the server. If I try to change it to pdmdc.pdmsource.local I get this...
NSChange.JPG
0
Paul MontgomeryBusiness IT ProfessionalAuthor Commented:
Would this be the issue? The full computer name is just pdmdc.local rather than pdmdc.pdmsource.local

serverdomain.JPG
0
JohnBusiness Consultant (Owner)Commented:
It well could be. Looking at a properly set up server, the name is the full form as you suggest. I have not renamed a server (never any need) but I think you can.
0
Justin YeungSenior Systems EngineerCommented:
if that's the only DC in domain (it is virtual i believe) and nothing is in the AD,
I will recommend to toast it and rebuild from scratch, change DC name is not fun.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Paul MontgomeryBusiness IT ProfessionalAuthor Commented:
I looked at another server as well and that's where I noticed the difference. I did begin to make the change just to see how far I could get and was stopped by grayed out choices. There might be a way in powershell but I don't have a clue as to how.
0
JohnBusiness Consultant (Owner)Commented:
I tend to agree with the idea of rebuilding the server as it appears it was not set up properly to begin with.
0
Paul MontgomeryBusiness IT ProfessionalAuthor Commented:
FYI John, here's a good guide on how to do that.

I'll wait until others comment on whether that could be the issue or not before I try it.
0
Paul MontgomeryBusiness IT ProfessionalAuthor Commented:
Justin, I wouldn't mind trying it anyway. Do you think that is what is causing the issue?
0
JohnBusiness Consultant (Owner)Commented:
Yes I know you can change the name but a number of things are affected. That I why I agreed with the other expert.
0
Paul MontgomeryBusiness IT ProfessionalAuthor Commented:
Also to start over wouldn't it be just a matter of removing the DNS role and recreating it or would it not handle the AD properly? If not what would you recommend for redoing the DC?
0
Paul MontgomeryBusiness IT ProfessionalAuthor Commented:
Actually thinking this through and reading your comments again it sounds like starting from scratch is the road to take (just read Justins post as it came late). In any case thanks for sticking with me on this. Any suggestions on accepting solutions?
0
JohnBusiness Consultant (Owner)Commented:
If you are going to rebuild then accept the posts that helped make your decision.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.