Hello I am currently testing the compatibility of our organization with Windows 11 and I am facing a strange behavior. The DNS service is not working well with Windows 11. On Windows 10 there is no issue and all the IP addresses are resolved correctly from our DNS, but on Windows 11, the DNS results are strange: If the request belongs to our main domain, nslookup provides the correct internal IP address If the request belongs to an internal domain only, nslookup provides the correct internal IP address If the request belongs to any other domain, nslookup provides the public IP address instead of the internal IP address This is only happening from the internal network. If I connect by VPN, using the same DNS servers, then the result is correct in every case. Has anybody experienced the same issue? Is this a problem of the Windows 11 desktop, the DNS server...? Thanks in advance Best regards Yann

Dear all I have found a solution that solve my issue but generate a bigger concern. I have just tried to configure manually the network connection of the laptop, using exactly the same IP address, mask, gateway and dns server that I was getting before from the DHCP server. And it works! Like this the DNS is correctly providing the internal IP address instead of the external one. If I then configure back the network through DHCP, it fails again. It looks like if the DHCP server is giving more information than just the IP configuration. Has anybody experienced this kind of issue? Thanks in advance Best regards Yann

The accepted answer is no solution for me (on Windows 11 Pro, 21H2 22000.978) My network adapter is set up to automatically discover the DNS server and my router at home is set up to supply a self-hosted local-network DNS server (192.168.178.21). When I'm at home, this DNS server is correctly discovered without manually configuring it on every device. However, if I join any other network (e.g. a public train network or our office network), the local-net DNS server at home is, obviously, not available; yet windows fails to attempt to discover a new one. Even if I do ipconfig /flushdns /registerdns or ipconfig /release /renew this issue persists. The only fix is to manually configure a publicly accessible DNS server (e.g. 1.1.1.1) every time I join another network and set it back to auto-discover when I come back home. Manually configuring this every time is NOT a good solution. Windows should discover a functioning DNS server when set to auto-discover.

If the request belongs to any other domain, nslookup provides the public IP address instead of the internal IP address Do you happen to have a public web site with the same name as internal domain? If so a split brain deployment may be needed. https://learn.microsoft.com/en-us/windows-server/networking/dns/deploy/split-brain-dns-deployment --please don't forget to upvote and Accept as answer if the reply is helpful--

Hello Patrick Thanks a lot for your answer. I will review it. But the strange thing is that we are having the correct behavior on Windows 10 client but it is failing on windows 11 client. Best regards Yann

As a work-around you could try adding an A record named "www" and point it to the public domain address. --please don't forget to upvote and Accept as answer if the reply is helpful--

Windows 11 - DNS issue

Yann Dublanche 111

Hello

I am currently testing the compatibility of our organization with Windows 11 and I am facing a strange behavior. The DNS service is not working well with Windows 11.

On Windows 10 there is no issue and all the IP addresses are resolved correctly from our DNS, but on Windows 11, the DNS results are strange:

If the request belongs to our main domain, nslookup provides the correct internal IP address
If the request belongs to an internal domain only, nslookup provides the correct internal IP address
If the request belongs to any other domain, nslookup provides the public IP address instead of the internal IP address

This is only happening from the internal network. If I connect by VPN, using the same DNS servers, then the result is correct in every case.

Has anybody experienced the same issue? Is this a problem of the Windows 11 desktop, the DNS server...?

Thanks in advance

Best regards

Yann

Accepted answer

Yann Dublanche 111 Reputation points

2021-10-28T16:17:06.307+00:00

Dear all

I have found a solution that solve my issue but generate a bigger concern.
I have just tried to configure manually the network connection of the laptop, using exactly the same IP address, mask, gateway and dns server that I was getting before from the DHCP server. And it works! Like this the DNS is correctly providing the internal IP address instead of the external one.

If I then configure back the network through DHCP, it fails again.

It looks like if the DHCP server is giving more information than just the IP configuration.

Has anybody experienced this kind of issue?

Thanks in advance

Best regards

Yann
Please sign in to rate this answer.

1 person found this answer helpful.
Anonymous

2021-10-28T17:41:15.89+00:00

I'd start a new thread for this new topic.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Siem Rood 5 Reputation points

2023-04-04T10:36:29.3666667+00:00

I experience the same issue here, DNS Server remains the same, dispite the fact that the DCHP server should provide one

Andrew 0 Reputation points

2023-07-26T14:51:38.79+00:00

We are experiencing a very similar issue in an enterprise deployment. Windows 10 is fine at that same network whereas Windows 11 doesn't resolve all queries for internal networks. Seems to have no issue resolving external queries but are set to internal DNS. It's very strange.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

12 additional answers

Kevin Gelking 21 Reputation points

2022-10-11T11:53:59.697+00:00

The accepted answer is no solution for me (on Windows 11 Pro, 21H2 22000.978)
My network adapter is set up to automatically discover the DNS server and my router at home is set up to supply a self-hosted local-network DNS server (192.168.178.21).

When I'm at home, this DNS server is correctly discovered without manually configuring it on every device.
However, if I join any other network (e.g. a public train network or our office network), the local-net DNS server at home is, obviously, not available; yet windows fails to attempt to discover a new one.

Even if I do ipconfig /flushdns /registerdns or ipconfig /release /renew this issue persists.
The only fix is to manually configure a publicly accessible DNS server (e.g. 1.1.1.1) every time I join another network and set it back to auto-discover when I come back home.

Manually configuring this every time is NOT a good solution. Windows should discover a functioning DNS server when set to auto-discover.
Please sign in to rate this answer.

4 people found this answer helpful.
Peter Kiertzner 0 Reputation points

2023-01-31T08:52:47.7333333+00:00

Hi Kevin.

I have the same problem and I use the same fix as you.

/Peter

Jason Dunstan 5 Reputation points

2023-04-18T17:15:06.18+00:00

Did you find a resolution to this? I have the exact same problem and it is so frustrating, considering this is such a basic kind of function.

Pablo Igualada 0 Reputation points

2023-12-14T22:03:22.7+00:00

I'm having the exact same issue. When I connect in my office with LAN, and come home with WIFI, even when I have DHCP, my laptop still uses office DNS servers. I need to setup manual DNS (public 8.8.8.8 for example), and switch back to automatic DNS, then it works. But this is really disturbing.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Anonymous

2021-10-24T21:18:24.337+00:00

If the request belongs to any other domain, nslookup provides the public IP address instead of the internal IP address

Do you happen to have a public web site with the same name as internal domain? If so a split brain deployment may be needed.
https://learn.microsoft.com/en-us/windows-server/networking/dns/deploy/split-brain-dns-deployment

--please don't forget to upvote and Accept as answer if the reply is helpful--
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Yann Dublanche 111 Reputation points

2021-10-25T07:28:58.943+00:00

Hello Patrick

Thanks a lot for your answer. I will review it. But the strange thing is that we are having the correct behavior on Windows 10 client but it is failing on windows 11 client.

Best regards

Yann
Please sign in to rate this answer.
Anonymous

2021-10-25T13:36:44.187+00:00

Sounds good, you're welcome.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Yann Dublanche 111 Reputation points

2021-10-25T13:52:46.943+00:00

Hello Patrick

I have reviewed it and everything is correct.
In fact, the AD DNS services only contains the internal IP addresses.
As a consequence, there is no reason it answers the public IP address.

Best regards

Yann
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Anonymous

2021-10-25T14:05:41.237+00:00

As a work-around you could try adding an A record named "www" and point it to the public domain address.

--please don't forget to upvote and Accept as answer if the reply is helpful--
Please sign in to rate this answer.
Yann Dublanche 111 Reputation points

2021-10-25T14:14:57.067+00:00

My mistake in my last reply. The AD DNS service only contains internal IP addresses, so should never reply the IP it is providing.

nslookup
Default Server: name.domain
Address: aa.aa.aa.aa

intranet.domain

Server: name.domain
Address: aa.aa.aa.aa

Non-authoritative answer:
Name: webproxy.domain
Address: bb.bb.bb.bb
Aliases: intranet.domain

Thanks

Yann
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Windows 11 - DNS issue

12 additional answers

Your answer