How to Fix DNS Server Not Responding

The “DNS server not responding” error can suddenly prevent websites from opening, even when your device appears connected to Wi-Fi or Ethernet. You may see this message in Windows Network Diagnostics, while Chrome may display errors such as “DNS address could not be found” or “DNS lookup failed.” Fortunately, the problem is usually connected to your router, DNS settings, network adapter, browser, VPN, or internet service provider.

DNS stands for Domain Name System, and its purpose is to translate website names into numerical IP addresses that computers can understand. When you enter a domain name into your browser, your device contacts a DNS server to locate the website. If that server is unavailable, overloaded, incorrectly configured, or blocked by another program, your browser cannot complete the connection.

In many cases, you can fix a DNS server not responding issue by restarting your router, clearing the DNS cache, changing your DNS provider, or resetting your network settings. You do not normally need advanced technical knowledge to complete these steps. It is best to begin with simple checks before changing system-level settings or contacting your internet service provider.

This guide explains how to fix DNS server not responding errors on Windows, macOS, Android, iPhone, Wi-Fi, and Ethernet connections. Work through the solutions in order and test your internet connection after each one. Once websites begin loading normally, you can stop without completing the remaining troubleshooting steps.

What Does “DNS Server Not Responding” Mean?

A DNS server not responding message means your device requested information from a DNS resolver but did not receive a usable response. Your internet connection may still be active, but the device cannot convert domain names such as example.com into the IP addresses required to reach those websites. This is why connected Wi-Fi does not always mean that browsing will work.

The error can affect every website or only certain domains, depending on its cause. A temporary router failure may block all DNS requests, while an outdated browser cache may affect only one website. Incorrect IPv4 or IPv6 settings, corrupted network configurations, unavailable DNS servers, and unstable wireless signals can also interrupt the domain name resolution process.

Sometimes the problem is outside your device. Your internet service provider’s DNS servers may be experiencing an outage, maintenance, congestion, or routing problems. In that situation, switching to another public DNS provider can restore access. However, you should first determine whether the error affects one device, several devices, one browser, or the entire network.

If every connected device cannot open websites, the router, modem, ISP, or assigned DNS server is probably responsible. If only one computer has the problem, its browser, network adapter, VPN, security software, or DNS configuration is more likely to be causing it. This simple distinction can prevent you from changing settings that are already working correctly.

Start with These Quick DNS Troubleshooting Checks

Begin by opening several reliable websites rather than testing only one page. A specific website may be temporarily unavailable even though your DNS connection is working normally. You can also open the same website in another browser or use a private browsing window. If it works there, your browser extensions, cached files, cookies, or secure DNS settings may be responsible.

Next, test the internet on another phone, tablet, or computer connected to the same network. When other devices work normally, focus on the device showing the DNS error. When none of them can browse, restart the router and check the ISP connection. This quick comparison helps separate a local device problem from a network-wide DNS failure.

Switch between Wi-Fi and Ethernet if both options are available. A computer that fails on Wi-Fi but works through an Ethernet cable may have a weak wireless signal, faulty Wi-Fi driver, interference problem, or incorrect wireless adapter configuration. If Ethernet also fails, the DNS server, modem, router, operating system, or internet provider may require further troubleshooting.

You should also check whether airplane mode is disabled and your device is connected to the intended network. Forgetting and reconnecting to the Wi-Fi network can repair saved configuration problems. Enter the password again, allow the device to obtain a fresh IP address, and then reopen your browser to see whether domain names begin resolving correctly.

Restart Your Router, Modem, and Device

Restarting your equipment is one of the fastest ways to fix DNS server not responding errors. Routers and modems store temporary connection information that can become outdated or corrupted. A proper restart clears temporary network sessions, refreshes the public connection, renews DNS information, and allows your devices to request new local IP addresses from the router.

Turn off your computer or mobile device first. Unplug the router and modem from their power sources, then leave them disconnected for approximately 60 seconds. If you have a separate modem and router, reconnect the modem first and wait until its connection lights become stable. Reconnect the router afterward and allow it to complete its startup process.

Once the network equipment is fully online, restart your computer or phone and reconnect to Wi-Fi or Ethernet. Open several websites to test the connection. Avoid pressing the small factory-reset button during this process because it can erase your network name, Wi-Fi password, ISP credentials, parental controls, port forwarding rules, and other customized router settings.

If restarting temporarily fixes the problem but the DNS error keeps returning, your router firmware, power supply, heat level, or DNS configuration may need attention. Place the router in a ventilated location and check its administration panel for firmware updates. An older or unstable router may also struggle when many devices are connected simultaneously.

Clear the DNS Cache on Windows

Windows saves recent DNS lookup results in a local cache so websites can load faster. However, cached records can become outdated, corrupted, or inconsistent with a website’s current server configuration. Flushing the DNS cache forces Windows to discard stored records and request fresh information from the configured DNS resolver.

To flush DNS on Windows 10 or Windows 11, search for “Command Prompt,” right-click it, and choose “Run as administrator.” Enter ipconfig /flushdns and press Enter. Windows should display a message confirming that the DNS Resolver Cache was successfully flushed. Close the browser completely, reopen it, and test the affected websites.

You can also renew the device’s IP configuration when flushing DNS alone does not work. Open an administrator Command Prompt, enter ipconfig /release, and then run ipconfig /renew. The first command releases the current IP address, while the second requests a new configuration from the router’s DHCP service.

After renewing the connection, run ipconfig /flushdns once more and restart the computer. These commands are especially useful when the DNS error appeared after changing routers, switching networks, waking the computer from sleep, installing a VPN, or reconnecting after an internet outage. They do not delete personal documents, applications, or browser bookmarks.

Reset Winsock and TCP/IP Settings

Winsock is a Windows component that controls how applications communicate with network services. VPN software, malware removal tools, security programs, network utilities, and damaged system settings can corrupt the Winsock catalog. When this happens, browsers may fail to reach DNS servers even though Windows reports that the device is connected to the internet.

Open Command Prompt as an administrator and enter netsh winsock reset. Next, run netsh int ip reset to restore important TCP/IP settings. Restart the computer after both commands have completed because the reset will not take full effect until Windows reloads its networking services and rebuilds the necessary configuration.

After restarting, reconnect to your network and test several websites. Windows may automatically recreate standard network settings, but manually assigned IP addresses or DNS servers may need to be entered again. Users on workplace, school, or managed networks should record their original configuration or contact the network administrator before performing a TCP/IP reset.

A Winsock reset is more advanced than clearing the DNS cache, so it should be used after basic fixes fail. It is particularly helpful when every browser shows a connection error, newly installed network software caused the issue, or other applications cannot access online services. If only one browser is affected, reset that browser before resetting the entire Windows network stack.

Change Your DNS Server on Windows

Your internet provider normally assigns DNS servers automatically, but those servers can become slow or temporarily unavailable. Changing to a reputable public DNS resolver may improve reliability and resolve repeated DNS server not responding errors. Popular options include Google Public DNS at 8.8.8.8 and 8.8.4.4, or Cloudflare DNS at 1.1.1.1 and 1.0.0.1.

On Windows 11, open Settings, select Network & Internet, choose Wi-Fi or Ethernet, and locate the DNS server assignment option. Select Edit, change the setting from Automatic to Manual, and enable IPv4. Enter your chosen preferred DNS server and alternate DNS server, save the changes, and reconnect to the network.

Windows 10 users can open Control Panel, choose Network and Internet, select Network and Sharing Center, and click Change adapter settings. Right-click the active Wi-Fi or Ethernet adapter, select Properties, and open Internet Protocol Version 4. Choose “Use the following DNS server addresses,” enter the new DNS addresses, and save the configuration.

After changing the DNS settings, clear the DNS cache and restart your browser. Do not combine addresses from several providers unless you understand how fallback resolution works. Keep a record of the original automatic setting so you can restore it if the new resolver causes problems with local devices, parental controls, workplace networks, or region-specific services.

Disable VPN, Proxy, and Security Software Temporarily

VPN applications route your internet traffic through remote servers and often apply their own DNS configuration. If the VPN server is unavailable or its DNS protection feature fails, your browser may show a DNS lookup error. Disconnect the VPN completely, close its application, and test the internet using your normal network connection.

A manually configured proxy server can create a similar problem. On Windows, open Settings, go to Network & Internet, and select Proxy. Disable manual proxy settings unless your employer, school, or network administrator requires them. On macOS, proxy options are available under the active network connection’s advanced settings.

Firewalls and antivirus programs can also block DNS traffic after an update, configuration change, or false-positive detection. Temporarily pause third-party security software and test the connection, but turn protection back on immediately afterward. If disabling it fixes the error, update the program or restore its default network rules rather than leaving the computer unprotected.

Browser extensions that manage privacy, filtering, advertising, or encrypted connections may interfere with DNS requests as well. Open the browser in private mode or temporarily disable extensions one at a time. If the problem disappears, remove or update the extension responsible. Avoid disabling multiple security tools permanently just to keep websites loading.

Update or Reinstall the Network Adapter Driver

The network adapter driver allows Windows to communicate with Wi-Fi and Ethernet hardware. An outdated, incompatible, or corrupted driver can cause DNS errors, random disconnections, missing networks, and limited internet access. Driver problems commonly appear after a Windows update, hardware change, system recovery, or installation of network management software.

Right-click the Start button, open Device Manager, and expand Network adapters. Right-click your active wireless or Ethernet adapter and select Update driver. Allow Windows to search automatically, but also check the computer or adapter manufacturer’s support page when Windows reports that the best driver is already installed.

You can reinstall the adapter when updating does not help. In Device Manager, right-click the network adapter, choose Uninstall device, and restart the computer. Windows normally detects the hardware and reinstalls a compatible driver during startup. Download the correct driver beforehand when working on a device that may not reconnect automatically.

Another simple option is to disable and re-enable the adapter. Open the network connections panel, right-click the active adapter, choose Disable, wait several seconds, and select Enable. This restarts the network interface without rebooting the entire computer and may repair a connection that became stuck after sleep, hibernation, or switching between networks.

Fix DNS Server Not Responding in Chrome

Chrome may display DNS-related messages even when other browsers continue working. Start by opening the affected website in an Incognito window. If it loads, clear Chrome’s cached files and cookies or disable recently installed extensions. You can also restart Chrome completely by closing every browser window and ending remaining Chrome processes in Task Manager.

Chrome includes a Secure DNS feature that may use a resolver different from your operating system’s DNS settings. Open Chrome Settings, select Privacy and Security, choose Security, and locate the Secure DNS option. Turn it off temporarily or choose another supported provider, then restart the browser and test the connection again.

You can also clear Chrome’s internal DNS and socket information. Enter chrome://net-internals/#dns in the address bar and use the available option to clear the host cache when supported by your browser version. Then open chrome://net-internals/#sockets and flush the socket pools before reloading the website.

If Chrome remains the only affected browser, reset its settings to their original defaults. This disables extensions, clears temporary configurations, and restores standard startup and search settings without normally deleting bookmarks or saved passwords. Reinstalling Chrome should be considered only after browser reset, extension testing, and system-level DNS troubleshooting have failed.

Clear the DNS Cache on macOS

macOS also maintains a DNS cache that can contain outdated records. To clear it, open Terminal from Applications and Utilities. Enter sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder, press Return, and provide the administrator password when requested. Terminal may not display a confirmation message even when the command completes successfully.

Restart the browser after flushing the cache and test several websites. If the problem continues, open System Settings, select Network, choose the active Wi-Fi or Ethernet connection, and review its DNS configuration. Remove unfamiliar DNS addresses unless they were intentionally added by your employer, school, VPN provider, or network administrator.

To add another DNS resolver, open the DNS section of the active connection, select the option to add a server, and enter a trusted DNS address such as 1.1.1.1 or 8.8.8.8. Apply the changes, disconnect from the network, and reconnect so macOS can begin using the updated resolver.

You can also forget the Wi-Fi network and join it again when the saved connection profile is damaged. Select Wi-Fi in System Settings, open the known networks list, remove the affected network, and reconnect using its password. This can correct invalid IP addresses, old DNS values, and network settings carried over from a previous router.

Fix DNS Problems on Android and iPhone

On Android, turn airplane mode on for several seconds and then switch it off. Restart the phone and reconnect to Wi-Fi before changing advanced settings. If one wireless network causes the problem, forget that network and join it again. You can also test mobile data to determine whether the issue belongs to the phone or router.

Recent Android versions may include a Private DNS option under Network and Internet settings. If a custom hostname is configured incorrectly or its provider is unavailable, set Private DNS to Automatic or Off temporarily. You may also use a trusted provider hostname, but the exact menu name varies between manufacturers and Android versions.

On an iPhone, open Settings, select Wi-Fi, tap the information icon beside the connected network, and choose Configure DNS. Change it to Automatic or manually enter a trusted resolver. You can also select Renew Lease to request fresh network information from the router before restarting the iPhone and testing Safari again.

If DNS errors affect every Wi-Fi network on the phone, reset the device’s network settings. Be aware that this removes saved Wi-Fi networks, passwords, VPN configurations, and certain cellular settings. Use this option only after restarting, forgetting the network, disabling VPN services, and testing another internet connection.

Check the Router’s DNS and DHCP Settings

Your router distributes IP addresses, gateway information, and DNS settings to connected devices through DHCP. If its DHCP service stops working correctly, devices may receive invalid network information or fail to obtain a DNS server. Log in to the router’s administration panel and confirm that DHCP is enabled for a normal home network.

Review the router’s internet or WAN settings to see which DNS servers it is using. You can normally choose automatic DNS from the ISP or enter a public resolver manually. Changing DNS at the router level applies the selected addresses to most connected devices, making it useful when the error affects the entire household.

Avoid changing unrelated settings such as VLANs, PPPoE credentials, subnet masks, routing tables, or MAC address options unless you understand your ISP’s requirements. Incorrect WAN settings can disconnect the entire network. Before editing anything, take screenshots or write down the original values so they can be restored accurately.

Install router firmware updates only through the manufacturer’s official administration interface or support page. Firmware updates can repair stability, compatibility, security, and DNS forwarding problems. Keep the router powered during the update because interrupting the process may damage the device and require recovery or replacement.

Determine Whether Your ISP Is Causing the DNS Error

When every device on the network loses access at the same time, the internet provider may be experiencing an outage. Check the modem’s internet, broadband, DSL, or optical connection light. A red, blinking, or missing connection indicator can suggest a line, authentication, signal, or service problem rather than a device-level DNS configuration issue.

Try accessing a website through mobile data instead of home Wi-Fi. You can then check your provider’s service status page or verified support channels. Neighbours using the same ISP may also confirm whether the interruption is widespread. Avoid repeatedly resetting devices when the provider has already acknowledged a regional outage.

Contact the ISP when the modem does not establish a connection, public DNS servers do not help, or the problem continues on every device after a complete restart. Explain when the issue began, which lights appear on the modem, whether Ethernet works, and which troubleshooting steps you have completed.

The provider may refresh your connection, check signal levels, replace faulty equipment, correct account provisioning, or investigate DNS and routing failures. If the problem occurs frequently, ask whether the supplied router or modem needs replacement. Repeated short outages can indicate failing equipment even when the connection eventually returns by itself.

Use Windows Network Reset as a Last Resort

Windows includes a Network Reset feature that removes and reinstalls network adapters while restoring many settings to their defaults. This can fix deeply corrupted configurations that remain after DNS flushing, driver updates, and TCP/IP resets. However, it may also remove saved adapter settings and require network software to be configured again.

On Windows 11, open Settings, select Network & Internet, choose Advanced network settings, and open Network reset. On Windows 10, the option is available under Network & Internet and Status. Select Reset now, save your work, and allow the computer to restart when prompted.

After the reset, reconnect to Wi-Fi, re-enter the network password, and test your browser. You may also need to reinstall VPN clients, virtual network adapters, or specialized software. Devices using static IP addresses, custom DNS settings, or workplace configurations should record those details before proceeding.

Use Network Reset only when the error affects multiple applications and the earlier solutions have failed. It is unnecessary when a single website is unavailable or one browser is malfunctioning. A full reset should correct local configuration problems, but it cannot repair an ISP outage, damaged router, disconnected cable, or external DNS service failure.

How to Prevent DNS Server Errors in the Future

Keep your operating system, browser, network drivers, router firmware, VPN client, and security software updated. Compatibility issues often appear when one network component is significantly older than the others. Regular updates can correct bugs that cause failed DNS queries, dropped Wi-Fi connections, and conflicts between security features.

Use a reliable DNS provider and avoid installing unknown programs that change proxy, VPN, or DNS settings. Some free applications and browser extensions reroute traffic without clearly explaining the change. Review installed network tools occasionally and remove anything you no longer recognize, trust, or use.

Restart the router occasionally, especially if it remains powered on continuously and supports many connected devices. Keep it in a cool, open location away from enclosed cabinets and heat-producing electronics. Excessive heat, overloaded hardware, and unstable power adapters can cause repeated network failures that appear to be DNS problems.

Record any custom DNS addresses, router settings, static IP details, and ISP credentials before changing them. Having a copy of the original configuration makes troubleshooting safer and faster. If the error returns regularly, note the time, affected devices, network type, and solution that worked so you can identify a consistent pattern.

Final Thoughts

The fastest way to fix DNS server not responding errors is to begin with a full router and device restart. You should then test another browser and device, clear the DNS cache, renew the IP address, and temporarily disable VPN or proxy services. These basic steps resolve many temporary DNS and network connection failures.

If the problem continues, switch to a reliable public DNS server, reset Winsock and TCP/IP settings, and update the network adapter driver. Browser-specific problems may require clearing the host cache, changing Secure DNS settings, disabling extensions, or restoring the browser to its default configuration.

A network-wide failure usually points toward the router, modem, assigned DNS server, or internet service provider. A problem affecting only one device is more likely connected to its operating system, adapter, browser, VPN, firewall, or saved network configuration. Identifying the scope of the failure is often the most important troubleshooting step.

Avoid performing a factory reset unless every safer option has failed and you have saved the necessary router information. Most DNS problems can be solved without deleting personal data or replacing equipment. By following the fixes in order, you can restore website access while minimizing unnecessary changes to your network.

Frequently Asked Questions

Why does my internet work but the DNS server does not respond?

Your device may be connected to the router while the DNS resolver is unavailable or incorrectly configured. The connection exists, but websites cannot load because domain names are not being translated into IP addresses.

What is the fastest way to fix a DNS server not responding?

Restart the router and device, then clear the DNS cache and reconnect to the network. If the error remains, change the preferred DNS server to a trusted public resolver.

Is it safe to change my DNS server?

Yes, using a reputable public DNS provider is generally safe. Record the original automatic setting so you can restore it if the new resolver affects workplace tools, local devices, or restricted services.

Can a VPN cause a DNS server error?

Yes, a VPN may use its own DNS servers or block normal DNS requests when its connection fails. Disconnect the VPN, close its application, and test the internet through your standard connection.

Does resetting the router fix DNS problems?

Restarting the router can clear temporary DNS, DHCP, and connection errors. A factory reset may also help in rare cases, but it erases customized settings and should only be used as a final option.