How To • %category% • %subcategory%

How to change DNS on Windows safely

This guide will walk you through safely changing the Domain Name System (DNS) settings on your Windows computer. You'll learn how to switch to a different DNS server, which can often improve browsing speed, enhance privacy, or resolve website access issues. The process involves adjusting network adapter properties and verifying the change.

Note: Steps may vary by device and router model. This guide focuses on safe, general methods.

Quick Answer

Open Settings, go to Network & Internet, and click on "Change adapter options".
Right-click your active network connection (Wi-Fi or Ethernet) and select "Properties".
Select "Internet Protocol Version 4 (TCP/IPv4)" and click "Properties".
Choose "Use the following DNS server addresses" and enter your preferred DNS (e.g., 1.1.1.1 for Cloudflare).
Click "OK", close the windows, and open Command Prompt as administrator.
Run the command ipconfig /flushdns to clear the old DNS cache.

If this doesn't work, follow the diagnostic flow below to pinpoint the issue.

What you need

Before you start

Administrator access on your Windows computer.
Your current DNS server addresses (usually obtained automatically).
The new DNS server addresses you want to use (e.g., 1.1.1.1, 8.8.8.8).
A working internet connection to verify changes.
Knowledge of whether you're on Wi-Fi or Ethernet.

Good to know

DNS translates website names to IP addresses.
Changing DNS can bypass ISP blocking or improve speed.
Some DNS services offer filtering (e.g., for malware or ads).
You can set DNS at the router level for all devices.
Always note original settings so you can revert if needed.

Diagnose the issue in 2 minutes

Is it only one device or all devices?
- One device: Likely a Windows DNS setting issue. Proceed with this guide.
- All devices: Problem may be with your router or ISP. Check router DNS settings.
Wi-Fi vs Ethernet:
- If both show the same DNS issue, it's probably not a adapter-specific problem.
DNS vs no connection:
- Can you ping an IP address? Open Command Prompt and run ping 1.1.1.1.
- If ping works but ping google.com fails, it's a DNS issue.
VPN on vs off:
- Turn off VPN. If DNS works, the VPN may be overriding your DNS settings.
Router vs ISP:
- Check if other devices on the same network have the same problem.
- If yes, log into your router and see if DNS is set manually there.

Quick checks:

Run ipconfig /all in Command Prompt to see current DNS servers.
Use nslookup google.com to test DNS resolution.
Restart your router and computer to clear temporary glitches.

Step-by-step guide

Step 1 — Open Network Settings

Access the network configuration area in Windows.

Click the Start menu and open "Settings" (the gear icon).
Go to "Network & Internet".
Select "Status" from the left sidebar.

What you should see: A page showing your network connection status, including Wi-Fi or Ethernet details.

Step 2 — Access Adapter Options

Navigate to the classic network adapters window.

Scroll down and click on "Change adapter options".
A new window will open showing your network connections (e.g., Wi-Fi, Ethernet).

What you should see: Icons for each network adapter on your computer.

Step 3 — Open Properties of Your Active Connection

Select the connection you are currently using.

Right-click on the active adapter (it should not have a red "X").
Choose "Properties" from the context menu.

What you should see: A properties dialog box with a list of items.

Step 4 — Select Internet Protocol Version 4 (TCP/IPv4)

Find the networking protocol that handles DNS.

In the list, scroll and find "Internet Protocol Version 4 (TCP/IPv4)".
Click on it to highlight it, then click the "Properties" button below.

What you should see: A new window with options for IP and DNS settings.

Step 5 — Enter New DNS Server Addresses

Switch from automatic to manual DNS configuration.

Select the option "Use the following DNS server addresses".
Enter your preferred DNS server in the "Preferred DNS server" field (e.g., 1.1.1.1 for Cloudflare).
Optionally, enter an alternate DNS server in the "Alternate DNS server" field (e.g., 1.0.0.1).
Ensure "Validate settings upon exit" is checked for safety.

What you should see: The DNS fields become editable, allowing you to type in numbers.

Step 6 — Apply Changes and Close

Save the new DNS settings.

Click "OK" in the TCP/IPv4 properties window.
Click "OK" in the adapter properties window.
Close the network connections window.

What you should see: The windows close, and your connection might briefly disconnect and reconnect.

Step 7 — Flush the DNS Cache

Clear old DNS entries to ensure the new settings take effect.

Search for "Command Prompt" in the Start menu, right-click it, and select "Run as administrator".
In the Command Prompt window, type ipconfig /flushdns and press Enter.
You should see a message confirming the DNS resolver cache was flushed.

What you should see: A success message: "Successfully flushed the DNS Resolver Cache."

Step 8 — Test the New DNS

Verify that the DNS change is working correctly.

Open a web browser and visit a few websites to ensure they load.
In Command Prompt, run nslookup google.com to see which DNS server is responding.
Check that the server listed matches the one you set.

What you should see: Websites load normally, and nslookup shows your new DNS server address.

OS-specific notes:

Windows: The steps above are for modern Windows versions (10 and 11). Older versions may use Control Panel > Network and Sharing Center.

macOS: Go to System Preferences > Network, select your connection, click Advanced, and go to the DNS tab.

Linux: Typically done via network manager GUI or by editing /etc/resolv.conf (requires root).

Common fixes by symptom

Connected but no internet

Likely causes:

Incorrect DNS server addresses entered.
Firewall or antivirus blocking DNS queries.
Router DHCP not providing valid DNS.

Safe fixes:

Revert to automatic DNS to test connection.
Disable firewall temporarily to check.
Restart your router and computer.

When to stop: If reverting to automatic DNS restores internet, the manual DNS may be unreachable.

Some websites don’t open

Likely causes:

DNS server filtering or blocking certain sites.
Local hosts file redirecting domains.
Browser cache or extensions interfering.

Safe fixes:

Try a different DNS server (e.g., switch from 8.8.8.8 to 1.1.1.1).
Clear browser cache and cookies.
Check hosts file for unusual entries.

When to stop: If the issue persists across multiple DNS servers, it may be a website problem.

Slow speed on Wi-Fi only

Likely causes:

Wi-Fi interference or weak signal.
DNS queries taking longer over Wi-Fi.
Router prioritizing Ethernet over Wi-Fi.

Safe fixes:

Move closer to the router or reduce obstructions.
Change Wi-Fi channel to less crowded one.
Test with Ethernet to compare speeds.

When to stop: If Ethernet works fast, the issue is likely Wi-Fi, not DNS.

High ping spikes

Likely causes:

DNS server latency or overload.
Network congestion on your ISP side.
Background downloads or updates.

Safe fixes:

Switch to a DNS known for low latency (e.g., Cloudflare).
Limit bandwidth-heavy applications.
Ping your router to check local network health.

When to stop: If ping spikes continue after DNS change, the problem may be beyond DNS.

VPN breaks local devices

Likely causes:

VPN overriding DNS settings to its own servers.
Split tunneling not configured properly.
Local network access blocked by VPN.

Safe fixes:

Check VPN settings for DNS leak protection or custom DNS.
Configure split tunneling to exclude local traffic.
Disconnect VPN to test local connectivity.

When to stop: If VPN always causes issues, consider changing VPN provider or settings.

IP conflict

Likely causes:

Multiple devices with same IP on network.
Static IP set manually conflicting with DHCP range.
Router DHCP server malfunctioning.

Safe fixes:

Release and renew IP via ipconfig /release and ipconfig /renew.
Restart router to clear DHCP leases.
Set device to obtain IP automatically unless advanced setup is needed.

When to stop: If conflicts recur, adjust router DHCP settings or set static IPs outside the DHCP range.

Quick reference

Metric	What it means	Good baseline
Latency (Ping)	Time for data to travel to server and back. Lower is better.	< 50 ms for gaming, < 100 ms for browsing.
Jitter	Variation in latency. Causes audio/video stutter.	< 30 ms for stable VoIP/video calls.
Packet loss	Percentage of data packets lost in transit. Should be near zero.	0% ideal, < 1% acceptable for most uses.
Throughput	Actual download/upload speed. Affected by network congestion.	Close to your ISP plan speed (test via speed test).
Signal strength	Wi-Fi signal power in dBm. Higher (less negative) is better.	-50 dBm excellent, -70 dBm acceptable, below -80 dBm poor.

Setting	Safe baseline	Notes
Wi-Fi security	WPA2 or WPA3 (AES encryption)	Avoid WEP or open networks. Use strong password.
DNS	1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) as backup	Change if default ISP DNS is slow or blocks sites.
Router admin	Change default login, enable automatic updates if available.	Keep firmware updated to patch security holes.
Guest network	Enable for visitors, separate from main network.	Isolates IoT devices for better security.
Updates	Check monthly for OS, router, and driver updates.	Updates often include network stability fixes.

Mind map summary

Change DNS on Windows
|
├── Why change?
│   ├── Speed: Faster resolution
│   ├── Privacy: Less logging
│   ├── Access: Bypass blocks
│   └── Reliability: Backup servers
|
├── Before you start
│   ├── Admin rights required
│   ├── Note current DNS
│   └── Choose new DNS (e.g., 1.1.1.1, 8.8.8.8)
|
├── Steps
│   ├── Open Settings > Network & Internet
│   ├── Change adapter options
│   ├── Right-click active connection > Properties
│   ├── Select IPv4 > Properties
│   ├── Enter manual DNS
│   ├── Apply and close
│   ├── Flush DNS cache (ipconfig /flushdns)
│   └── Test with nslookup and browsing
|
├── If it doesn't work
│   ├── Diagnose: One device vs all devices
│   ├── Check: Ping IP vs domain
│   ├── Verify: VPN off, router restart
│   └── Revert: Automatic DNS as fallback
|
└── Safety
    ├── Use reputable DNS providers
    ├── Keep original settings noted
    ├── Avoid public DNS if privacy critical
    └── Escalate to ISP if issues persist

Troubleshooting checklist

Device

Check DNS settings are correct in network adapter.
Flush DNS cache with ipconfig /flushdns.
Disable firewall/antivirus temporarily.
Update network drivers.
Restart the computer.

Router

Restart the router.
Check router DNS settings (if set globally).
Verify DHCP is enabled and providing DNS.
Update router firmware.
Change Wi-Fi channel if interference suspected.

ISP

Test connection with automatic DNS.
Run speed test during different times.
Check for ISP outages in your area.
Contact ISP if DNS changes don't resolve issues.
Ask if they block alternative DNS servers.

When to escalate

Contacting ISP: If internet is down despite correct settings on all devices, or if speed tests consistently show far below plan. Also, if DNS changes cause persistent connection drops.
Replacing router: If router frequently loses settings, overheats, or fails to provide connectivity even after resets and firmware updates. Older routers may not support modern DNS standards.
Asking IT support: If on a managed network (office, school), do not change DNS without permission. Escalate if network policies block required sites or services.

What to collect before escalating

Speed test results (screenshots or notes).
Timestamps of when issues occur.
Error messages (e.g., "DNS server not responding").
List of steps you've already tried.
Model numbers of router and network adapter.

FAQ

Is changing DNS safe?

Yes, changing DNS is generally safe. It's a standard network configuration. However, always use reputable DNS providers to avoid malicious servers that could log your data or redirect you to fake sites.

You can revert to automatic DNS at any time if you encounter problems.

What are the best DNS servers to use?

Popular public DNS servers include Cloudflare (1.1.1.1), Google (8.8.8.8), and OpenDNS (208.67.222.222). Choose based on speed, privacy policies, and additional features like parental controls.

It's a good idea to test a few with tools like DNS benchmark to see which is fastest for your location.

Will changing DNS increase my internet speed?

It can improve browsing speed if your ISP's DNS is slow or overloaded. DNS affects how quickly website addresses are resolved, not your raw download speed. For streaming or large downloads, bandwidth is more critical.

In many cases, switching to a faster DNS reduces the time it takes for websites to start loading.

Do I need to change DNS on every device?

No. You can change DNS at the router level to apply it to all devices on your network. Alternatively, change it only on specific devices where you want different DNS settings.

Changing on Windows affects only that computer. Other devices will use the router's DNS unless configured separately.

Why does my DNS keep reverting to old settings?

This can happen if your router's DHCP is overriding manual settings, or if network troubleshooting tools reset adapters. Check that you saved the settings correctly and that no group policies (on work networks) are enforcing specific DNS.

Running commands like netsh int ip reset in admin Command Prompt can sometimes fix persistent issues.

Can I use IPv6 DNS servers?

Yes. In the network adapter properties, you can also configure "Internet Protocol Version 6 (TCP/IPv6)" with IPv6 DNS addresses (e.g., Cloudflare's 2606:4700:4700::1111). This is recommended if your ISP supports IPv6.

Leaving IPv6 on automatic is usually fine, but setting manual IPv6 DNS can provide consistency.

What does flushing DNS cache do?

Flushing the DNS cache clears locally stored DNS mappings. This forces your computer to query DNS servers anew for website addresses, which can resolve issues where old or corrupted entries cause sites not to load.

It's a safe operation and often one of the first troubleshooting steps for DNS problems.

How do I know if my DNS change worked?

Use the nslookup command in Command Prompt. Type nslookup google.com and check the "Server" line—it should show the DNS server you set. Also, visit websites to ensure they load correctly.

If nslookup shows a different server, you may need to flush DNS cache or restart your computer.

Sources and references

Windows networking documentation from Microsoft (TCP/IP configuration guides)
Apple support articles on macOS network settings
Linux manual pages for resolv.conf and network manager
Router vendor generic setup guides (e.g., TP-Link, Netgear, Asus)
IEEE 802.11 standards overview for Wi-Fi basics
Networking diagnostics fundamentals (ping, traceroute, nslookup)
DNS protocol explanations from IETF RFC documents
Security best practices for home networks (WPA3, strong passwords)
Public DNS provider documentation (Cloudflare, Google Public DNS)
General computer networking textbooks and online courses

Menu

How to change DNS on Windows safely

AI Assistant

Was this tool helpful?