Understand What Changing DNS Actually Does
Changing the DNS server in Windows 11 changes the service that translates internet domain names into network addresses. When you enter a familiar website name in a browser, the operating system or application must obtain information that allows it to locate the destination. A recursive DNS resolver helps answer that question. Our introduction to DNS explains the underlying process.
A different resolver can help when your existing resolver is unavailable, responds slowly or provides incorrect results. It can also let you use a deliberately chosen filtering service or encrypted DNS arrangement. It does not increase the physical speed of a slow Wi-Fi link, replace your internet provider or inherently improve the speed of every website.
Consider a computer that can reach a known online service when given its actual network address but cannot resolve several ordinary public domain names. That pattern makes DNS a relevant area to investigate. A computer that cannot communicate with any destination because its network adapter is disconnected has a different problem. Changing the resolver cannot establish a missing network connection.
DNS is also distinct from the IP address assigned to your computer and the default gateway it uses. On Windows 11, you can normally edit DNS server assignment independently of your ordinary IP configuration. There is no need to invent a static IP address, subnet mask or gateway merely to specify a different DNS service.
Some organizations use DNS for internal systems, secure access and filtering. Replacing an approved resolver in that environment may prevent applications from finding their intended resources. Establish that the network is yours or you have permission to change the computer’s DNS settings before proceeding. The steps in this guide focus on authorized personal or otherwise approved Windows 11 configurations.
Check The Connection And Record The Original DNS Settings
Start by confirming that the computer connects to the expected network. If it is connected to Wi-Fi, check the network name and ordinary connection status. For Ethernet, confirm that the correct cable and network connection are in use. Compare another trusted device on the same network if you suspect a wider service interruption.
Our Wi-Fi connected without internet guide and Ethernet connection guide explain how to distinguish an internet outage from a problem limited to one computer. DNS is only one possible cause of an inaccessible website.
Before changing the adapter settings, open a normal PowerShell session and enter this read-only inventory command:
Get-DnsClientServerAddressReview the output for the adapter you actually use, including the IPv4 and IPv6 entries. Microsoft describes the available inspection and configuration commands in its DNS Client module reference. A system can list several physical and virtual adapters, and not all of them are relevant to the current connection.
Also inspect the adapter’s DNS assignment in Settings. Record whether it is Automatic or Manual and note the exact existing addresses and encryption options. The addresses displayed by PowerShell do not by themselves establish whether they were manually entered or received through DHCP. Record both the source and the values so that you can restore the previous arrangement accurately.
If the existing DNS addresses belong to a VPN, office network or managed configuration, ask its administrator before replacing them. Keep your notes offline or in a location you can reach even if the next change temporarily interrupts connectivity. A reliable rollback plan is more valuable than making several changes quickly and hoping one succeeds.
Choose A Resolver Based On Your Actual Requirements
A public DNS service is one option, not a requirement. The resolver provided by your internet service or network administrator may work well and may be needed for local network resources. If your existing service is functioning normally, there is no universal reason to replace it.
For an authorized public DNS configuration, two widely used providers document these ordinary, non-family-filtered resolver addresses:
| Resolver | Preferred IPv4 | Alternate IPv4 | IPv6 Pair |
|---|---|---|---|
| Cloudflare | 1.1.1.1 | 1.0.0.1 | 2606:4700:4700::1111 2606:4700:4700::1001 |
| Google Public DNS | 8.8.8.8 | 8.8.4.4 | 2001:4860:4860::8888 2001:4860:4860::8844 |
The values above come from the providers’ own Windows setup documentation and Google Public DNS setup guide. Verify that the service you select is suitable for your particular device and network. Other providers and separately designated filtering services have their own addresses and policies.
Compare availability, intended filtering behavior, privacy practices and compatibility with the network you need to use. Select both preferred and alternate addresses from the intended service when consistency matters. Combining providers can result in different answers or filtering behavior when the system consults a different resolver.
An advertised resolver response time is not necessarily representative of your connection. Geography, routing, cached information and the particular query can affect observed performance. Do not rely on a single claimed speed ranking or assume one provider is universally fastest.
Also distinguish privacy from anonymity. Choosing another resolver changes which service receives DNS requests; it does not prevent every other party from observing your internet activity. Examine the provider’s terms and data practices, especially if your work involves sensitive information. Only configure services whose operation and policies fit your needs.
Change DNS Through Windows 11 Settings
Use the ordinary Windows Settings interface when it is available. This is a convenient way to update only DNS for the intended network without manually assigning an IP address. Save work before modifying the connection, particularly if you are connected to the computer remotely.
- Open Settings using Windows + I and select Network & internet.
- For Ethernet, open the relevant connection properties. For Wi-Fi, select the connected network or its hardware and connection properties, depending on your Windows release.
- Locate DNS server assignment. Choose Edit beside that label, not the separate IP assignment control.
- Change the assignment method to Manual. Enable the IPv4 or IPv6 section you intend to configure and enter the approved addresses in the corresponding preferred and alternate fields.
- Review the encryption options if they appear. Save the configuration and verify that normal network communication still works.
For a typical authorized IPv4 configuration using Cloudflare’s ordinary resolver, the preferred address would be 1.1.1.1 and the alternate address would be 1.0.0.1. If you select a different provider or a specific approved filtering service, use that service’s documented matching pair instead.
Microsoft’s network settings guide explains the distinction between automatic network assignment and manual configuration. Keep your existing IP assignment unchanged when you are only editing DNS. The exact placement of the DNS controls can differ between Windows 11 builds and types of connections.
If the interface does not present a DNS server assignment control, use the supported adapter properties approach described next or the appropriate administrator-approved procedure. Do not enter unfamiliar values into unrelated gateway or subnet fields. After saving, inspect the displayed settings and test the actual network. Do not move directly to a router-wide change merely because the first computer’s settings are difficult to find.

Configure DNS Using The Network Adapter Properties
Windows also provides traditional network adapter configuration controls. This approach is useful on versions or configurations where the newer Settings interface does not expose the intended DNS fields. It requires particular care because the same properties dialog contains IP address settings unrelated to DNS.
Press Windows + R, type ncpa.cpl and open Network Connections. Identify the correct active adapter, such as Wi-Fi or Ethernet. Right-click it and open Properties if you are authorized to administer the machine. Do not select a virtual adapter solely because it appears first in the list.
Select Internet Protocol Version 4 (TCP/IPv4) and open its Properties. In the DNS portion of that dialog, select Use the following DNS server addresses if an approved manually specified resolver is appropriate. Enter the IPv4 preferred and alternate values. Leave the ordinary IP address assignment fields exactly as they were unless your administrator has provided a separate IP configuration change.
For IPv6, use the separate Internet Protocol Version 6 (TCP/IPv6) properties and its appropriate DNS fields. An IPv6 address does not belong in the IPv4 fields. Similarly, do not attempt to type an ordinary IPv4 pair into a dialog intended exclusively for IPv6.
Confirm the selected settings and close the applicable properties dialogs. Use the original network connection and run the verification checks later in this article. If you find that a manually configured DNS list already exists in an advanced dialog, record it and consult the appropriate network documentation before replacing it.
Google’s public resolver instructions document the traditional adapter-properties route. Keep in mind that corporate software, VPN configuration and network policy may supply additional rules not visible in a single dialog. If the relevant options are unavailable, obtain approved assistance instead of changing adapter permissions or attempting to defeat management controls.
Handle IPv4 IPv6 And DNS Encryption Correctly
IPv4 and IPv6 are two address families used for network communication. DNS server addresses are entered using the format expected by the corresponding settings section. A machine can use both address families, and changing only one family’s DNS addresses may leave another available resolver configuration in place.
Check your existing adapter information before changing either family. If the network supports IPv6 and your intended resolver supplies IPv6 addresses, configure those through the appropriate IPv6 controls when required by your chosen arrangement. Do not disable IPv6 simply to force the system to prefer a particular public resolver. A device or network may depend on IPv6 for normal operation.
Windows 11 can provide DNS over HTTPS settings for compatible resolver configurations. DNS over HTTPS protects DNS traffic in transit between the client and a compatible resolver using HTTPS. It does not encrypt every other part of an internet connection or make the resolver unaware of the requests it handles.
When the DNS settings offer encrypted options, follow the selected provider’s official documentation. A supported automatic template may be available for recognized resolvers. Do not invent an encryption endpoint or assume that every manually entered address supports the same encryption method. If a choice permits fallback to unencrypted queries, understand that those requests may not receive the same transport protection.
Check your organization’s rules before enabling encryption or selecting a new resolver. A managed network may depend on approved inspection and name resolution arrangements. Changing DNS transport to evade those controls is not an appropriate troubleshooting step.
Also consider browser-specific secure DNS and VPN settings. Some applications can use their own resolution path or receive DNS through an established tunnel. The setting visible in Windows is therefore not proof that every application uses precisely that resolver. Verify the intended scope of the configuration rather than treating one successful browser test as evidence about all system traffic.
Change The Resolver With PowerShell When Appropriate
PowerShell provides an alternative for authorized administrators who need a reproducible configuration. Use it from a local session if possible. Changing network settings on a computer you administer remotely can disconnect the session, so arrange a supported alternative access path before making that change.
First identify the network adapters and their actual interface indexes:
Get-NetAdapter | Select-Object Name, InterfaceIndex, StatusThen inspect the existing resolver values:
Get-DnsClientServerAddressChoose the interface index corresponding to the intended active adapter. The number in the next example is illustrative and must not be blindly copied. In an authorized elevated PowerShell session, a configuration using Google Public DNS IPv4 addresses might be:
Set-DnsClientServerAddress -InterfaceIndex 12 -ServerAddresses ("8.8.8.8","8.8.4.4")Replace 12 with the actual interface index. Microsoft documents this command in the Set-DnsClientServerAddress reference. Manually specified server addresses override the automatic resolver assignment for the targeted interface. Assess both address families and the network’s requirements before issuing changes.
Check the result with the inspection command again, and examine the entry for the intended interface:
Get-DnsClientServerAddress -InterfaceIndex 12Again, use your actual index. The absence of output from a configuration command is not by itself a complete verification. Inspect the resulting values and test a real name query. These examples do not establish a DNS over HTTPS configuration; transport settings have their own supported controls.
Do not run the modified command against every adapter or pipe a list of all interfaces into it unless that broad change is specifically intended and authorized. Leave VPN and virtual networking interfaces alone unless their documented configuration requires attention. For most personal devices, the Windows Settings route is simpler and makes the scope easier to understand.
Verify The New DNS Configuration With Real Queries
After saving the new resolver settings, verify that Windows has the intended configuration and that name resolution works. Start with a read-only query of the relevant adapter rather than assuming the change succeeded because the Settings dialog closed.
Open PowerShell and inspect Get-DnsClientServerAddress again. Find the intended interface and confirm the expected server addresses for each configured address family. If the output still shows unexpected values, investigate whether you selected the wrong adapter, whether a VPN is active or whether a policy has restored an approved configuration.
Run a normal public name query:
Resolve-DnsName example.comA result containing relevant DNS records demonstrates that the query obtained an answer through the applicable resolution process. The exact addresses should not be treated as permanent because records can change. To compare a specific reachable resolver directly, an example using the ordinary Cloudflare IPv4 address is:
Resolve-DnsName example.com -Server 1.1.1.1Only use that comparison on a network where querying that resolver is authorized. A direct server test demonstrates the result of that specific query; it does not prove that Windows or every browser normally uses the same service. Similarly, a successful DNS answer does not guarantee that the website itself is reachable or functioning.
Open a trusted website in your usual browser and verify an ordinary page. If the browser uses its own secure DNS setting, note that distinction. Check any authorized internal resources required for work, such as a network file service, before treating the new configuration as ready for routine use.
Avoid testing using confidential hostnames belonging to an organization unless its approved procedures permit the query. The public example domain is sufficient for an ordinary connectivity comparison. If the new configuration fails, use the recorded original settings to restore service. A successful configuration must preserve the network functions you actually depend on, not just resolve one public name during the test.
Clear Cached DNS Information Only When Useful
Windows can retain DNS results temporarily so that it does not have to repeat every lookup immediately. This behavior is normal and can improve efficiency. When diagnosing a recently corrected name resolution problem, a cached answer may make it more difficult to observe what the new resolver returns.
If you have a reason to clear the Windows DNS client cache, use the supported command in a Command Prompt session:
ipconfig /flushdnsAlternatively, PowerShell offers Clear-DnsClientCache. These operations concern the Windows DNS client cache. They do not change the configured DNS server addresses or clear every cache maintained by a web browser, application or remote resolver.
After clearing the cache, repeat the same non-sensitive name query and check the ordinary website or service that was affected. Record the result. If the domain currently has no appropriate record or the remote authoritative service is experiencing a problem, clearing your local cache cannot create a valid answer.
A direct query to a specific resolver and an ordinary application lookup may behave differently because of application settings, caching or name-resolution policy. Use the appropriate tool for the question you are trying to answer instead of assuming that every lookup follows one simple path.
Do not turn cache flushing into a routine speed optimization. It can cause previously cached names to be queried again, and a functioning computer does not need constant manual cache clearing. Avoid combining it with unrelated commands that reset the network stack, remove saved Wi-Fi connections or change firewall settings.
If a particular application continues showing an outdated result while the ordinary system query works, consult the application’s documented behavior. Closing and reopening a browser or application may be reasonable after saving work, but do not clear its cookies, passwords or all browsing data just to perform a DNS comparison. Keep the repair targeted to the evidence.
Restore Automatic DNS Or Your Previous Manual Configuration
A safe configuration change includes a clear reversal procedure. If websites stop loading, approved internal resources disappear or the intended resolver is unavailable, return to the settings recorded before the change. Do not choose a new random DNS address in the hope of recovering the network.
In the Windows 11 Settings interface, revisit Network & internet, the intended adapter and DNS server assignment. When the original method was Automatic (DHCP), choose that method again and save. If the original configuration was Manual, restore the precise approved addresses and any applicable encryption preferences instead.
In the traditional adapter properties dialog, return the DNS choice to Obtain DNS server address automatically when that was the original configuration. For a manually configured network, re-enter the original values. Restore IPv4 and IPv6 as appropriate without changing the unrelated IP assignment setting.
An authorized administrator who originally used DHCP can restore the adapter’s automatic resolver assignment through PowerShell. The following uses the same illustrative interface index as before:
Set-DnsClientServerAddress -InterfaceIndex 12 -ResetServerAddressesUse the real interface index. The reset option is appropriate when returning to the default DNS settings supplied through the network, not when the previous manual addresses are required. If the earlier setup was manual, intentionally restore those recorded values using the supported configuration method.
Inspect the resulting addresses and repeat the ordinary name and website comparisons. If the computer uses a managed VPN or authentication arrangement, verify that its usual resources remain accessible as well.
If all devices on your network still experience internet failure after an appropriate rollback, investigate the shared connection rather than modifying each computer’s DNS separately. Our router and ISP troubleshooting guide describes that broader diagnostic. A reversible approach makes it possible to preserve dependable connectivity while investigating the original issue.
Know When A Different DNS Server Is Not The Solution
DNS changes cannot resolve every connectivity problem. A disconnected Ethernet cable, unstable wireless signal, exhausted mobile data allowance, website outage or application authentication failure can all make a service appear unavailable. Verify which part of the connection is failing before repeatedly switching resolvers.
If a single website fails while other public names resolve normally, compare the exact domain and error message. The website itself may be unavailable, its records may have changed, or access may be restricted for a legitimate reason. Do not use alternative resolvers to bypass an organization’s access controls.
If an internal office hostname no longer resolves after a public resolver was selected, restore the approved DNS arrangement and consult the administrator. Internal records may not exist in the public DNS system. Our VPN guide discusses separate network access considerations for private resources.
For networks that require a login webpage, unusual behavior may occur before that authentication completes. Use the network’s normal authorized login process and restore the expected network settings if necessary. Be cautious about entering sensitive credentials on untrusted connection pages.
If you want to change DNS for every device at home, understand that a router-wide configuration is distinct from changing one computer. It can affect televisions, mobile devices, guests and other equipment. Review the router’s documented options and obtain permission from other affected owners or administrators. Test on a single computer first when that is appropriate.
Document the final resolver, the reason for selecting it and the previous configuration. This article uses official Microsoft and resolver-provider documentation and original examples. Its illustrations are conceptual rather than Windows screenshots, and the commands were not independently executed on physical Windows 11 hardware for this article. The appropriate final settings depend on your network, authorization and actual connectivity requirements.
Frequently Asked Questions
Can I Change DNS Without Changing My IP Address?
Yes, Windows 11 provides separate DNS assignment controls. Leave the existing IP assignment and gateway unchanged when only changing DNS.
Which DNS Server Is Fastest For Windows 11?
There is no universal fastest server. Compare authorized services using your actual network and representative queries.
What Are Google’s Public DNS Addresses?
The ordinary IPv4 pair is 8.8.8.8 and 8.8.4.4. Google’s official setup guide lists the matching IPv6 addresses.
Should I Disable IPv6 To Change DNS?
No, disabling IPv6 is not required for an ordinary DNS change. Inspect and configure the appropriate address families.
Does DNS Over HTTPS Hide All Internet Activity?
No, it protects compatible DNS queries in transit, not all traffic or your identity from every party.
How Do I Undo A DNS Change?
Restore Automatic (DHCP) if that was the original method, or restore the previously recorded manual addresses and encryption options.
Will Changing DNS Fix Every Internet Problem?
No, DNS only addresses name resolution. Wi-Fi, routing, account access and website outages require separate diagnostics.


