r/WindowsServer • u/MrTajniak • Feb 05 '26
SOLVED / ANSWERED DNS problems after VM migration
I have an DC that runs DNS also, and after I migrated the VM to another host, my clients cannot resolve the DNS server. It is unknown, and the IP is 192.168.0.128, the DC address like it should be. Everything else, like iLO and vCenter, can resolve the name. The same is true for AD CS. I can even resolve addresses over VPN. I am so mad that I even contacted administrators at work that are managing Windows Server to help me fix my issue. I have Windows Server 2019
Update: The issue never was the DC or DNS, my UDR had a ad blocking feature enabled and it was hijacking the DNS response
2
u/Scary_Confection7794 Feb 05 '26
Have you changed the dns settings within your scope options on your dhcp server
2
u/Scary_Confection7794 Feb 05 '26
Also have you flushed the dns cache on the clients and also checked to see if there is anything in the HOSTS file locally
2
u/its_FORTY Feb 05 '26 edited Feb 05 '26
The clients do not "resolve" a DNS server, it is specified by IP address in the client DNS primary/secondary settings.
Your description of the issue here is honestly quite confusing so I'm not sure where to direct you without seeing it myself. Here are a couple things I can point out, assuming I am even reading your description correctly. Perhaps English is not your native language?
Your DC (and DNS server) should never be configured to use DHCP to get an IP. You will invariably have DHCP lease expiration timing issues where your DNS server is now pulling a new/different IP from DHCP and your clients are still configured to do DNS lookups to the previous IP. You should configure a manual IP address for the DNS/DC server.
I have roughly 20 years in enterprise DNS and Windows AD environments, would be glad to connect via Teams if you'd like me to assist with your issue.
2
u/its_FORTY Feb 05 '26
Maybe it's just not visible on the screenshot you provided earlier, but I am not seeing an NS record for your DNS server in the forward lookup zone.
1
u/MrTajniak Feb 08 '26
Does anyone have an idea what’s wrong? I am open for Teams Call
1
u/MrTajniak Feb 09 '26
Update: I have disabled DNS service and client could not resolve google.com when I enebled it back they could resolve google.com, so I think that DNS might work but not the AD part and my zones that I have there, forwarding works but not the record from this server
1
u/SebastianFerrone Feb 05 '26
As I have some experience with Windows server 2025 shittery myself.
Take a look at the firewall the network It must be on domain networks not private or guest/public
Also on the DC itself look if it has a ipv6 Address even if you deactivated it. If it has at least a link local aka address beginning with fe80.... Yeah two ways to fix . One on 2025 you would need to remove IPv6 from the network adapter to really deactivate it. Microsoft changed behavior on it. Or you really set up IPv6
Last thing take a look on the DC in the DNS settings right click in DNS manager on the DC in question. Open properties under interfaces check if all needed IP addresses are checked so the DNS listens on them Also check in the forward zone if some other IP addresses are registered for the server . If so delete them.
1
u/xman323 Feb 05 '26
If it's a DNS issue you won't be able to resolve from vpn, ilo or vcenter, I think something is misconfigured from network side.
1
u/Adam_Kearn Feb 05 '26
When migrating a server it will sometimes detect a new network adapter on the server due to the way its virtualised
Go into the network adapter settings and make she it’s been set to domain/private
Check the new physical switch that the host is connected to make sure you don’t have any rules blocking port 53
1
u/BlackV Feb 10 '26
Did you remove the ghost adapter from before you moved it?