Forum Discussion
Problem to setup DNS server on Windows Server 2016
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.
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.DNS MANAGERDNS MANAGERDNS MANAGERServer TCP/IPClient TCP/IPClient AddDomain
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
Hello,
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.
Thanks
Richard
Hello,
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.
Greetings.
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.
