How to Change a DNS Server: A Step-by-Step Guide 

To change a DNS server, open your network connection’s settings, replace the existing DNS server addresses with your chosen resolver (for example, 1.1.1.1 for Cloudflare), save, and flush the DNS cache. You can do this per device on Windows and macOS, or once at the router to apply it across every device on the network.

Key Takeaways

• Changing a DNS server takes a few minutes on Windows, macOS, or a router, and it can improve speed, security, and reliability.
• The fastest path is to set DNS at the device level (Windows network adapter properties, or macOS System Settings > Network > Details > DNS). Set it at the router to cover every device on the network at once.
• Popular public resolvers: Cloudflare (1.1.1.1), Google (8.8.8.8), Quad9 (9.9.9.9), and OpenDNS (208.67.222.222). Quad9 and Cloudflare add malware and phishing filtering.
• After changing DNS, flush the cache so the change takes effect: ipconfig /flushdns on Windows, sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder on macOS.
• Prerequisites: administrative rights on the device or router, and the IP addresses of the DNS provider you want to use. Estimated time: 5 to 10 minutes.

Changing a DNS (Domain Name System) server looks like a routine task, but it has an outsized effect on network performance, security, and reliability. Configured incorrectly, it can lead to slower connections, security gaps, or a complete loss of name resolution. Configured well, it is one of the quickest wins available to an IT team.

This guide explains why changing a DNS server matters, walks through step-by-step instructions for Windows, macOS, and routers, compares the major public resolvers, and covers the issues you are most likely to hit along the way.

Why You Need to Know How to Change a DNS Server

DNS is the phonebook of the internet. It translates human-friendly domain names like examplewebsite.com into the IP addresses machines actually use, so people can reach websites and services without memorizing numbers.

There are several scenarios where you will need to change it:

• Improving network performance. Switching to a faster or more geographically local resolver reduces latency and improves load times.
• Enhancing security. Providers like Cloudflare and Quad9 offer security-focused DNS that blocks known malicious domains, protecting users from phishing and malware.
• Preventing DNS hijacking. Properly configured DNS helps stop attackers from forging DNS records that send users to fake sites built to steal credentials. (See Cloudflare’s overview of DNS hijacking.)
• Troubleshooting connectivity. When a resolver has an outage or a misconfiguration, switching DNS is a fast way to isolate and resolve the problem.
• Customizing network behavior. Private or custom DNS servers let an organization enforce content filtering, control access, or manage internal resources.
• Managing client networks. For MSPs, configuring and optimizing DNS is part of keeping client networks reliable and secure.

Whether you are tuning for performance, enforcing a security policy, or chasing down a connectivity problem, knowing how to change a DNS server is a core IT skill.

Prerequisites

• Administrative rights on the device (or login access to the router’s admin interface).
• The DNS server IP addresses you want to apply (see the comparison table below).
• A few minutes per device, or one change at the router to cover the whole network.

Which DNS Provider Should You Use?

Most teams pick a public resolver based on whether they want raw speed, privacy, or built-in security filtering. Here is how the most common options compare:

For security-conscious environments, Quad9 and Cloudflare’s malware-blocking resolver (1.1.1.2) add a layer of protection at the DNS level. For straightforward speed, Cloudflare and Google are the common defaults.

How to Change a DNS Server on Windows 10 and 11

1. Open network settings. Right-click the network icon in the system tray and select Network & Internet settings. In Windows 11, go to Network & Internet > Advanced network settings > More network adapter options.
2. Open the adapter properties. Right-click your active connection and select Properties. Highlight Internet Protocol Version 4 (TCP/IPv4) and click Properties.
3. Enter the new DNS addresses. Select Use the following DNS server addresses, then enter a preferred and an alternate server (for example, 1.1.1.1 and 1.0.0.1 for Cloudflare). Click OK to save.
4. Verify the change. Open Command Prompt and run ipconfig /all. Confirm the DNS server entries match what you set.

How to Change a DNS Server on macOS (Ventura, Sonoma, Sequoia)

The path changed in macOS Ventura. Newer versions use System Settings and a Details button rather than the older System Preferences > Advanced flow.

1. Open network settings. Click the Apple menu, select System Settings, then click Network.
2. Select your connection. Choose your active connection (Wi-Fi or Ethernet) in the sidebar, then click the Details button next to it.
3. Open the DNS tab. Select DNS in the side list.
4. Add the new servers. Click the + button under DNS Servers and enter your chosen addresses (for example, 9.9.9.9 for Quad9). Use the – button to remove old entries.
5. Save. Click OK, then Apply if prompted.
6. Test it. Open Terminal and run ping example.com to confirm names resolve.

Note: On macOS Monterey and earlier, use System Preferences > Network, select the connection, click Advanced, then open the DNS tab.

How to Change a DNS Server on a Router

Changing DNS at the router applies it to every device on the network, which is the efficient choice for an office or a client site.

1. Log in to the router. Open the admin interface in a browser, usually at 192.168.1.1 or 192.168.0.1.
2. Find the DNS settings. Look under WAN, LAN, or DHCP settings. The exact location varies by model.
3. Enter the new servers. Add your chosen DNS addresses (for example, 208.67.222.222 for OpenDNS). Save and restart the router if prompted.
4. Verify. Check a device on the network to confirm it picked up the new DNS settings.

Troubleshooting Common DNS Change Issues

Issue: No internet connection after changing DNS. Cause: Incorrect or unreachable DNS server addresses. Fix: Re-check the entered addresses for typos and confirm the resolver is valid and reachable.

Issue: Slow or unresponsive DNS resolution. Cause: The chosen resolver is under heavy load or geographically distant. Fix: Test an alternative provider and pick the one with the lowest latency in your region.

Issue: Changes are not taking effect. Cause: Cached DNS entries or a stale network adapter. Fix: Flush the cache with ipconfig /flushdns (Windows) or sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder (macOS), then restart the device if needed.

Issue: The router ignores custom DNS settings. Cause: ISP-enforced DNS or incorrect router configuration. Fix: Check whether your ISP forces DNS. If it does, set DNS at the device level as a workaround.

Pro tips

• DNS over HTTPS (DoH). Most modern resolvers support encrypted DNS queries, which keep third parties from snooping on DNS traffic.
• Benchmark before you commit. Tools like GRC’s DNS Benchmark or Namebench help you find the fastest resolver for your location.
• Plan for IPv6. As networks adopt IPv6, add the provider’s IPv6 DNS addresses alongside the IPv4 ones.

How Syncro Fits Into This Workflow

Changing DNS on one machine takes a couple of minutes. Doing it across 50 or 500 endpoints, one device at a time, does not scale.

If you manage a fleet, you can push DNS changes and verify them remotely instead of touching each device. Syncro’s scripting engine lets you deploy a DNS configuration change across every managed endpoint on a schedule you define, and remote access lets you confirm and troubleshoot resolution without interrupting the user. For new client sites, network discovery maps what is on the network before you make changes.

DNS configuration is a fundamental network management task. Syncro gives IT teams and MSPs the scripting and remote management tools to update DNS settings across endpoints without touching each device individually.

---

By

Lindsey Giusto

I’m dedicated to continuously improving and innovating Syncro to help our partners successfully grow their business on our platform.

---

Share

• Share on Facebook
• Share on X
• Email this Page