Custom DNS servers can improve name resolution reliability, reduce lookup latency, or route internal hostnames to the correct addresses on managed networks. Incorrect DNS settings can make websites and internal services appear offline even when the network connection itself is working.
On Windows 11, DNS servers are configured per network adapter. The adapter typically receives DNS servers automatically from DHCP, but switching the DNS server assignment to manual overrides those values without changing the IP address configuration.
DNS changes apply only to the selected adapter, so wired and wireless connections can resolve names differently. Some VPN clients, endpoint security tools, or Group Policy settings can replace or lock DNS entries, and public resolvers may not work on networks that require internal DNS for split-horizon zones.
Select Automatic (DHCP) to revert to DNS provided by DHCP.
Manual DNS overrides the DHCP DNS list for the adapter. Incorrect servers prevent hostname resolution.
Use DNS servers approved by the network administrator.
Leave IPv6 disabled when the network does not provide IPv6 connectivity.
C:\> ipconfig /flushdns Windows IP Configuration Successfully flushed the DNS Resolver Cache.
Related: How to flush DNS cache in Windows
C:\> ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : workstation
Primary Dns Suffix . . . . . . . : example.invalid
##### snipped #####
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : example.invalid
DNS Servers . . . . . . . . . . . : 192.0.2.53
192.0.2.54
##### snipped #####
C:\> nslookup www.example.com Server: UnKnown Address: 192.0.2.53 Non-authoritative answer: Name: www.example.com Address: 93.184.216.34