07-02-2020 05:36 PM
07-02-2020 05:36 PM
After update to Windows 10 2004, I encountered following issue.
The computer set over 50 DNS suffixes cannot resolve DNS servers, and alternatively nslookup results "Address: 127.0.0.1".
If I remove some DNS suffix to be below 50, it works correctly.
This issue was not appear in Windows 10 1909.
I cannot find it as known issue here.
Does anyone know how to fix this issue?
07-06-2020 07:17 AM
Do you have any management software installed? For example, Cisco Umbrella works like that, rewrites the DNS to 127.0.0.1.
07-06-2020 06:35 PM - edited 07-06-2020 06:36 PM
Thank you for your reply.
This issue occurred without any management software.
In my environment, the administrator distributes DNS suffix search list as a following registry value via startup script and it contains 66 domains.
I know DNS suffix search list works correctly up to 50 in any Windows versions from before but they can resolve DNS server address if they have more than 50 DNS suffix search list domains.
In Windows 10 Version 2004
If DNS suffix search list contains 66 domains, it cannot resolve DNS server address correctly, so I cannot access any network resources.
*) The result of (Get-DnsClientGlobalSetting).SuffixSearchList shows only 50 domains but it has 66 domains in "SearchList" registry value.
In Windows 10 Version 1909
It can resolve DNS server address correctly.
I understand it is the best way to reduce DNS suffix search list domains but I would like to know the issue appears only my environment or not.
07-07-2020 05:34 AM
Thank you for your reply. This issue occurs without any device management application.
In my environment, the administrator distributes 66 domains to DNS suffix search list as following registry value via script although it works correctly only top 50 entries.
In Windows 10 1909
If it has 66 domains in DNS suffix search list, it can resolve DNS server address.
In Windows 10 2004
I cannot access any network resources because it cannot resolve DNS server address like below.
I know it is the best way to reduce the entries to under 50 but I would like to confirm this issue appears only my environment or not.
07-07-2020 12:18 PMSolution
I can confirm, the same happens on my 2004 Windows 10 computer.
Time to revise the dns entry list method :)