Disclosure: While we strive for independence and honesty in our unbiased reviews of repair guides, please note that some links on this page are affiliate links, meaning we
A ‘DNS server not responding’ error means the device could not translate a domain name into an IP address. The cause may be the device, router, configured resolver, VPN/security software or ISP—not the website itself.
Before you start
Write down Wi-Fi passwords, static IP settings, VPN profiles and custom DNS before resetting anything. Never download a ‘DNS repair’ executable from an ad.
Step-by-step
1. Check whether the outage is local
Open several sites on another device and switch one device between Wi-Fi and cellular. If every device fails, inspect modem/router status and the ISP outage page.
2. Restart the network cleanly
Power off modem and router, wait about 30 seconds, power the modem first, then the router. Avoid factory reset unless configuration and credentials are backed up.
3. Renew the client configuration
On Windows use the built-in troubleshooter, then an elevated terminal for ipconfig /flushdns and, if appropriate, ipconfig /release followed by ipconfig /renew. Restart afterward.
4. Change DNS only for a reason
Test a reputable resolver such as Cloudflare 1.1.1.1 or Google 8.8.8.8. Record the previous automatic/manual setting and keep IPv6 consistent.
5. Reset deeper components last
Update the network adapter driver from the device maker, inspect VPN/security software, then consider Windows Network Reset. This removes adapters and can require VPN reinstallation.
Troubleshooting the common failure points
Return to the last verified step and change one variable at a time. Record exact messages, device or browser version, network and account used. Restarting can clear a transient problem but should not replace diagnosis. Avoid registry cleaners, unofficial drivers, cracked apps and any support page that asks for remote access or payment before identifying itself.
How to confirm the result
Repeat the original action, then test a second realistic case. Confirm that settings survive a restart or sign-out where relevant. For account and financial actions, save the confirmation and review the official activity page. For hardware, inspect from normal viewing distance and avoid damage that could affect warranty eligibility.
FAQ
Is the first search result safe?
Not necessarily. Prefer the official product, government, bank, platform or device-maker page. Sponsored results and download mirrors can imitate legitimate support.
Should I pay for a repair or service?
Compare the expected benefit with replacement cost, warranty coverage and data risk. Get a written estimate for hardware and avoid paying to bypass a policy or security control.
What if the instructions look different?
Menus and policies change. Confirm the current version, region and account type in the official documentation.
Performance testing that can be repeated
Clone the same site, region, PHP version, theme, plugins and cache configuration. Measure cached and uncached TTFB, full-page load, Core Web Vitals and a controlled concurrency test from more than one location. Run several times across the day and report medians plus poor outliers. A vendor homepage benchmark or one empty WordPress install does not predict a real agency workload.
Resource limits behind the plan name
Ask about CPU, memory, PHP workers, processes, inodes, database connections, bandwidth and backup storage. ‘Unlimited websites’ normally shares finite resources. Review what happens at the limit: throttling, overage, forced upgrade or suspension. For client hosting, isolate noisy sites and document which party receives usage alerts before a campaign creates an emergency.
Staging and deployment workflow
Test one staging clone, database-safe deployment and rollback. A production push can overwrite orders, forms or comments if files and database are treated as one snapshot. Developers may need Git, SSH, WP-CLI, environment variables and log access; a friendly control panel is not a substitute. Record the release path so a contractor does not improvise on the live site.
Support under an actual incident
Open a ticket with a specific log excerpt and ask what the provider can inspect, change and restore. Managed hosting ranges from infrastructure assistance to hands-on WordPress troubleshooting; reseller support may not communicate with the agency’s clients. Confirm escalation, status-page history and emergency coverage before selling a service-level promise upstream.
Migration and DNS cutover
Inventory sites, databases, cron jobs, mail, certificates and DNS. Lower TTL in advance, copy and test through a temporary hostname or hosts-file entry, then synchronize changing data before cutover. Keep the old service available until SSL, forms, mail routing, redirects and analytics are verified. A free migration offer may exclude complex multisite, email or custom applications.
Backups and restore testing
A backup feature matters only when scope, frequency, retention and restoration are clear. Confirm whether databases, files, mailboxes and DNS are included, whether copies live in a separate failure domain and whether a single site can be restored without rolling back every client. Run a staging restore during the trial and record how long it takes; snapshots controlled by the same server are not a complete disaster-recovery plan.
When the cheaper option costs more
Low introductory prices can hide renewal increases, add-ons, usage overages and labor. Include implementation, migration, training, monitoring, backups and support in the comparison. A higher-priced product may be cheaper if it replaces several services or prevents manual errors; a feature-rich suite is wasteful when the team uses only its basic tier.
A maintenance schedule
Review users, failed automations, stale content, broken links and usage thresholds every month. Test backups and exports quarterly. Revisit pricing and terms before renewal. Assign an owner and a backup owner. Without a schedule, small configuration changes accumulate until nobody knows which integration, rule or source controls the live result.
Warning signs during evaluation
Be cautious when limits are described only as ‘fair use,’ support will not answer a specific scenario, an export omits key fields, or a vendor cannot explain renewal pricing. For financial and health topics, reject guarantees and personalized claims without evidence. For software, avoid abandoned downloads, unofficial installers and extensions whose permissions exceed their purpose.
Decision checklist
Write five non-negotiable requirements, three acceptable compromises and the maximum first-year cost. Score products only after eliminating those that fail a hard requirement. Give extra weight to reliability, support and reversibility. Re-run the choice when team size, transaction volume, legal obligations or the underlying product changes materially.
FAQ: what changes most often?
Prices, plan limits, promotional offers, integrations and platform policies change more frequently than core concepts. Check current official information at the point of action. A date in a title is not a promise that every third-party listing, coupon or compatibility claim remains valid.
What to document after choosing
Save the selected plan, implementation assumptions, renewal date, account owner, recovery method and the reason the runner-up was rejected. Record the first success metric and the condition that would trigger migration. This short decision record prevents future teams from repeating research or treating a temporary promotion as a permanent product advantage.
Support is part of the product
Submit one specific question during the trial and evaluate whether support understands the actual configuration. Locate the status page, escalation route and service commitments. Community forums can reveal workarounds, but they do not replace accountable help when a payment, account lockout, security incident or production outage affects real users.
Keep the pilot reversible
Use test data, a subdomain or a limited user group until the workflow is stable. Avoid a large annual prepayment, irreversible migration or public promise before the core task succeeds repeatedly. Reversibility lets the team reject a poor fit without defending sunk cost, and it turns experimentation into evidence rather than organizational disruption.
Final recommendation
Start with scope testing and a normal router restart, then flush/renew the client and test a reputable DNS resolver. Escalate to the ISP when multiple devices fail beyond the local network.
Editor’s Pick. Our team’s current top recommendation for this category. (Affiliate link coming soon — we only link programs we’ve vetted.)
