DNS Server Not Responding? Prove the Cause Before Changing Settings
DNS translates names into addresses. If domain names fail while basic IP connectivity works, DNS becomes a strong suspect. If the router and every IP are unreachable, repair the connection first.
Confirm it is actually a DNS failure
Open several unrelated sites and note the exact browser or Windows error. Compare another device on the same network. One website failing may be a site outage; one device failing suggests its configuration; every device failing suggests the router, upstream resolver or internet link.
Check whether the router gateway is reachable and whether the device obtained a valid address rather than a self-assigned one. A successful connection to a known IP while names fail supports a DNS diagnosis, but do not use random IPs or disable security controls to test.
Check DHCP, gateway and resolver assignment
Inspect the active adapter's IP address, default gateway and DNS servers. Home devices normally receive them through DHCP. Duplicate static settings, an expired lease or the wrong adapter can send queries nowhere.
Reconnect Wi-Fi or renew the lease using the operating system's supported network controls. On Windows, flush the DNS resolver cache after recording the error; this removes cached answers but does not change the authoritative DNS zone or internet plan.
Remove local interception one layer at a time
Browsers can use DNS over HTTPS independently of Windows, while VPN, proxy, antivirus web scanning, parental control and ad-blocking software may redirect DNS. Compare another browser, then pause one layer at a time only when organizational policy permits.
Check date, time and time zone because secure DNS and HTTPS rely on certificate validation. Do not permanently disable antivirus, firewall, IPv6 or encrypted DNS simply because one test changes the symptom; identify the responsible component and update or configure it safely.
Test the router and upstream DNS
If every device fails, check router WAN status and modem lights. Restart the router once using its normal procedure, wait for WAN registration, and confirm that DHCP is distributing reachable resolvers. Avoid factory reset because it can erase ISP, voice and Wi-Fi configuration.
Temporarily compare a reputable resolver such as the ISP's documented DNS or a well-known privacy-reviewed public service. Record the original automatic or manual values. Use only verified addresses from the provider's official site; malicious DNS can redirect traffic.
Understand what changing DNS can and cannot fix
A different resolver may improve lookup reliability or latency and can change which CDN node is selected. It does not increase subscription bandwidth, repair weak Wi-Fi, remove packet loss or restore a failed WAN.
If only one domain returns the wrong or missing record across multiple independent resolvers, its owner may have a DNS-zone problem. Preserve the domain, record type, time and resolver results instead of repeatedly changing household settings.
Escalate with useful evidence
Contact the ISP when all devices using automatic ISP settings fail, WAN status is abnormal or multiple reputable resolvers are unreachable. Provide times, device count, wired versus Wi-Fi results, assigned DNS addresses and router lights.
For managed work or school networks, give the evidence to IT. Split DNS, filtering and internal names may be intentional, so replacing corporate DNS can break access or violate policy. Never publish internal domain names or addresses in public reports.
Frequently asked questions
Will changing DNS make my internet faster?
It may shorten some name lookups or improve resolver reliability, but it does not raise the connection's bandwidth.
Is flushing the DNS cache safe?
It normally removes temporary local lookup results; the system queries them again. It does not delete files or change domain ownership.
Why do messaging apps work while websites report DNS errors?
An app may keep an existing connection or use different endpoints while the browser needs new DNS, TLS and proxy steps.
Should I disable IPv6 to fix DNS?
Not as a permanent first step. Compare configurations carefully and fix the broken resolver, router or ISP path instead of broadly disabling IPv6.
Verify the connection and latency before and after any DNS change.
Test network connection