DNS Suffix issue after update to Windows 10 2004

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 remov...

IstvanffyZ
Jul 07, 2020
Toru_Saito

I can confirm, the same happens on my 2004 Windows 10 computer.
Time to revise the dns entry list method 🙂

Regards,
Zoltan

IstvanffyZ

Brass Contributor

Jul 06, 2020

Toru_Saito

Do you have any management software installed? For example, Cisco Umbrella works like that, rewrites the DNS to 127.0.0.1.

Regards,

Zoltan

Toru_Saito

Copper Contributor

Jul 07, 2020

IstvanffyZ
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.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\SerachList

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.