02-19-2018 01:33 AM
02-19-2018 01:33 AM
I have problem to setup my DNS server on Windows Server 2016 Standard.
But from beginning.
I have installed Hyper-V 2016, on this I create Virtual Machine, and setup there Windows Server 2016.
My ActiveDirectory works fine, and I want to add DNS server.
I follow many tutorials on YouTube, and everyone have more folders/files in DNS Manager, on forward zone to be exactly.
I have attached 2 screens:
Can I ask for help? Because I can't figure it out. I dont have ideas.
I was reinstalling AD, DNS and nothing.
Thank You in advance,
02-19-2018 07:35 AM
Do you have any machine configured to actually use this new DNS server? I am guessing that you have just created the DNS server using the wizard. you are now looking in the DNS zone but do not see any records? Try setting the servers IP manually and point it to the new DNS server or use 127.0.0.1.
Hope that helps
If I can help more let me know.
02-19-2018 12:18 PM
By default your new domain controller is also a DNS server. Are you adding a second one? Make sure the new DC and all clients or members have the static address of DC listed for DNS and no others such as router or public DNS.
02-20-2018 12:12 AM
I would like to ask. Yes, I have install fresh AD with DNS Server.
My server has IP 192.168.xxx.201 so I put it into primary DNS on server, secondary DNS is empty.
On Client, I have IP 192.168.xxx.210 so I put primary DNS 192.168.xxx.201 and secondary DNS is empty.
Here are some screenshots. I will write about it now.
02-20-2018 12:34 AM
From the second machine. are you able to ping the IP address of the DNS server?
I am thinking perhaps it could be an issue with your Hyper-V setup and the Virtual Switches.
02-20-2018 01:05 AM
Yes, Im able to ping server and domain.
What should I bring from Hyper-V setup and virtual switch to help me finally connect computer to domain.
02-20-2018 01:11 AM
Have you tried manually creating the dns record to see if you are then able to connect to the domain, etc?
It could be an issue with dynamic DNS registration rather than Network as you are able to ping the DC.
02-20-2018 01:20 AM
No, because I don't know how could I create second DNS.
I was searching, but no info about.
02-20-2018 01:41 AM
In dns manager on the dc. Right-click on your forward lookup zone and click New Host (A or AAA). Enter the second vm's name and its IP address.
Let me know how that goes.
02-20-2018 01:58 AM
Thank You, but I dont have second VM, i got one VM where is Windows Server 2016, and laptop (client) with Windows 10.
Maybe You were talking about Hyper-V ?
02-20-2018 02:06 AM
Is the laptop running Hyper-V?
It might be best to create another VM say running windows 10 pro and try joining that to the domain.
You may have issues if you join your laptop to a dc that is running on it.
02-20-2018 02:13 AM
Okay, I will try. But, what if I would like to have this server in work and add other computers ?
02-20-2018 05:39 AM
A couple of things;
I'd change from 16 bit to 24 bit mask on both server and client.
Also check that both DC and problem client got the domain firewall profile on network connection,
When you do the domain join also try using just the domain NetBIOS name
02-20-2018 07:37 AM
I have change form 16 to 24 bit subnet but no change.
I have install second VM named W8Client, added host to DNS Manager (Name:W8Client, FQDN: W8Client.komplex.local, IP: 192.168.88.198) and can't join to domain. Its the same error what is on my Windows 10 laptop. (DNS Server name doesnt exist).
I try to join only with NetBIOS name. Okay, I saw that I need to write user and password. But I can't join.
02-20-2018 08:02 AM
Dcdiag /v /c /d /e /s:DCName >c:\dcdiag.log
(please replace DCName with your Domain Controller name)
ipconfig /all > C:\dc1.txt
ipconfig /all > C:\client.txt
also include C:\Windows\debug\netsetup.log (from problem client)
then put files up on OneDrive and share a link.
02-20-2018 08:30 AM - edited 02-20-2018 09:13 AM
DC and problem client should have the static address of DC listed for DNS and no other, so I'd remove 192.168.88.211
Client is mult-homed which will be problematic. I'd try diabling the other connections at least for domain join.
02-20-2018 08:40 AM
02-20-2018 10:32 AM
On .211 is running Hyper-V.
So, primary DNS should be 127.0.0.1 and secondary IP of Windows Server so 192.168.88.201 yes ?