DNS Resolution Error in Search Console? How to Fix Crawling

1. What Does a DNS Resolution Error in Search Console Mean?

Quick Answer: A DNS resolution error means Google asked the internet’s address book where your domain lives and got no answer, or a wrong one. Googlebot never reached your server, so it could not fetch any page. Search Console flags it as a host problem when more than 5% of DNS lookups fail on a single day.

Every visit starts with a DNS lookup: “Which server holds this domain?” If your nameservers are wrong, down or missing, nobody answers. To Google, the whole site has disappeared, even if the server is running fine.

Google’s Crawl Stats report help page checks host status in three parts over roughly 90 days: robots.txt fetching, DNS resolution and server connectivity. It treats a DNS failure rate above 5% of requests on any day as an issue. The error can surface in several places:

New to the tool? Read our plain-English explainer on Google Search Console. For other messages, see our guide to crawl errors in Search Console.

2. What Causes DNS Resolution Errors? Causes Ranked by Likelihood

Quick Answer: For Malaysian SMEs, the most common cause is a lapsed domain after a failed renewal card or a reminder sent to an old email. Next come nameserver or A record mistakes after a hosting move, then DNS provider outages, then firewalls blocking Google’s DNS queries.

When clients bring us DNS resolution errors, most turn out to be admin slips, not attacks.

What each cause looks like in practice:

• Expired domain. The renewal card expired, or the RM invoice went to an ex-staff email. A lapsed .my domain stops resolving for everyone, not just Google.
• Hosting move gone wrong. A typo in the new nameservers, or the old DNS zone deleted before the new one was live. Common during a redesign or a domain name change.
• Provider outage. Your DNS host went down for a few hours. The site recovers on its own, but Search Console records the failures.
• Blocked queries. A firewall or strict security setting drops Google’s requests, or allows UDP but not TCP DNS traffic.

If Google reaches your server but is refused, that is a different issue: see our guide to the Access Forbidden (403) error in Search Console.

3. Is the DNS Error Still Happening? How to Check in 10 Minutes

Quick Answer: Open Search Console, go to Settings, then Crawl stats, then Open report, and click the DNS resolution host status. A yellow icon means the problem is in the past. A red icon means it happened this week. Then run a live URL test to see whether Google can reach the site right now.

Search Console reports lag by a few days, as our guide on why Search Console data lags explains. Confirm the current state with these checks:

1. Read the host status. Click Settings, then Crawl stats, then Open report. Open Host status, then DNS resolution, and note the dates of spikes above the red dotted line.
2. Run a live test. Paste your home page into the URL Inspection bar and click Test live URL. A successful fetch means the DNS problem has cleared.
3. Check the domain status. Look up the domain on WHOIS (MYNIC runs it for .my domains). Confirm the expiry date and that the listed nameservers match what your host gave you.
4. Test from outside your office. Load the site on mobile data. Office routers often cache old DNS answers and hide the problem.

The live test steps follow Google’s URL Inspection tool help article.

4. How to Fix a DNS Resolution Error Step by Step

Quick Answer: Renew the domain if it lapsed, then make sure the nameservers at your registrar match your DNS host, and that the A or CNAME records point to your live server. Allow Google’s DNS queries through your firewall, wait for the change to spread, and confirm with a live URL test in Search Console.

Google’s own guide to debugging network and DNS errors for Google’s crawlers sets out the core checks. Here is the order we use for Malaysian SME sites:

1. Renew the domain first. Check the expiry at your registrar. If it lapsed, pay the renewal (most bill in RM by card or FPX) and update the card on file. Nothing else works until this is done.
2. Match the nameservers. At the registrar, confirm the nameservers are exactly the ones your DNS host gave you. One wrong character breaks every lookup.
3. Check the A and CNAME records. The root domain’s A record must point to your server’s public IP, and a www record must exist. Remove any record pointing to a private IP.
4. Test from the command line. Your developer can run dig example.com and dig example.com ns (with your domain) to confirm the answers match.
5. Open the firewall to Google. Ask your host to confirm Google’s crawler IP ranges are not blocked, and that DNS allows both UDP and TCP requests.
6. Speed up propagation. Google notes changes can take up to 72 hours to spread worldwide. Use Google Public DNS’s Flush Cache page for your main domain first, then for www.
7. Confirm in Search Console. Run Test live URL on the home page and two key pages. When the fetch succeeds, click Request indexing for your most important URLs.

If your site also stopped loading for visitors, work through our checklist for a website that is down and not loading. If the DNS now works but browsers show a security warning, the new server may lack a certificate; our guide to the SSL protocol error covers that next step.

5. How Long Does Google Take to Recover After a DNS Fix?

Quick Answer: DNS changes can take up to 72 hours to spread. Googlebot usually returns to normal crawling within days of a clean fix, and the red host status turns yellow after a week without failures. Pages that dropped out of the index typically return over one to four weeks, but Google gives no guarantee.

Recovery happens in stages. Use this table instead of refreshing Search Console every hour.

A yellow host status after the fix is normal: Google remembers a failure from over a week ago. Don’t keep changing DNS to “clear” it; each change restarts propagation.

6. Do DNS Errors Hurt Your Google Rankings?

Quick Answer: A short DNS blip of a few hours rarely moves rankings. Google slows crawling right away, and if pages stay unreachable for days, already-indexed URLs can be removed from the index. Longer outages mean slower recovery, so the duration of the failure matters more than the error itself.

Google’s DNS troubleshooting guide says DNS errors are treated much like server errors: crawling slows at once, and unreachable indexed pages can be dropped within days. Impact grows with outage length:

After a long outage, resubmit your sitemap; our guide to sitemap errors in Search Console helps if it fails. Also watch for soft 404 errors from half-restored pages or a stray “Page with redirect” status if the new host forces a different URL version.

7. How to Stop DNS Errors Coming Back

Quick Answer: Turn on auto-renewal with a card that will not expire soon, send registrar notices to a shared company inbox, keep the domain under the company’s own account, use a reliable DNS host, and record every DNS change. Add an uptime monitor so you hear about failures before Google does.

Repeat DNS errors usually trace back to ownership and admin gaps. This checklist closes them:

• Own the domain properly. Register it under the company name with SSM details, in an account the business controls, not a freelancer’s personal login.
• Auto-renew for multiple years. Renew two to five years ahead and set a calendar reminder 60 days before expiry as a backup.
• Use a shared inbox. Point registrar and hosting notices to an address such as admin@ that more than one person reads.
• Log every DNS change. Note the date, record and person. Any Search Console spike can then be matched to a change in seconds.
• Plan hosting moves. Lower the record TTL a day before a move, keep the old server running until the new DNS has spread, and never delete the old zone first.
• Monitor uptime. A free uptime checker pinging your home page every few minutes flags outages fast.

Keep Search Console access in company hands too. If locked out, see how to regain ownership of Search Console. A DNS move can also break your verification TXT record, which our guide to Search Console verification failures covers.

8. When Should You Call in an SEO Team?

Quick Answer: Escalate if the live URL test still fails 72 hours after your fix, if you cannot log in to the registrar or DNS host, if errors keep returning every few weeks, or if organic traffic has not recovered within a month. These point to deeper hosting, access or indexing problems.

Get help early in these situations:

• No access. The domain sits in an ex-vendor’s account and nobody has the login.
• Repeat failures. The host status keeps going red, which usually means an unreliable DNS or hosting setup.
• Mixed signals. DNS is fixed but pages show robots.txt or redirect issues, such as “Indexed, though blocked by robots.txt” or a 404 error on key pages.
• Knock-on platform problems. Ad platforms may refuse ads that point to a dead landing page, as in “ad set can’t be published” errors on Meta, and video indexing issues can surface once crawling resumes.

Your Google Business Profile stays live during a DNS outage because Google hosts it. Still check it: fix profile photos that are not showing, and act fast if the listing was wrongly marked permanently closed on Google.

ZenWeb is a Google Partner agency that has worked with 500+ Malaysian businesses. Our SEO services team handles DNS checks, index recovery and reporting.

9. Conclusion

A DNS resolution error in Search Console looks alarming, but it usually has a simple cause: a lapsed domain, a mistyped nameserver or a short outage. Confirm whether it is still happening, fix the domain, nameservers, records and firewall in that order, then let Google recrawl. Most sites are back to normal crawling within a week. For broader help keeping your site visible, start at the ZenWeb home page.

10. Frequently Asked Questions

1. Why does Search Console show a DNS error when my site loads fine?

The error may be from a past outage: yellow means more than a week ago, red means this week. Your device may also be using a cached DNS answer. Run Test live URL to see what Google gets now.

2. Can I request a recrawl after fixing a DNS error?

Yes. Once Test live URL succeeds, click Request indexing for key pages. There is a daily limit, so prioritise your home page and service pages, and resubmit your sitemap for the rest.

3. Will a DNS resolution error give my site a Google penalty?

No. A DNS error is not a penalty and does not appear under Manual actions. Google simply cannot reach the site, so crawling slows and unreachable pages may drop out. Rankings usually return once the site is reachable and recrawled.

4. How long does DNS take to update after I change records?

Google’s documentation says DNS changes can take up to 72 hours to spread worldwide. Many updates show within a few hours. You can speed up Google’s side by flushing your domain on Google Public DNS’s Flush Cache page.