DNSSEC SERVFAIL after changing nameservers
Diagnose DNSSEC failures after a nameserver move, compare validating DNS responses, and repair the delegation before changing crawler rules.
By Crawlito · 6 min read
In short
- An old registrar DS record can conflict with a new DNS provider's keys.
- A DNS failure occurs before the server can return HTML or robots.txt.
- Compare validation behavior and repair the delegation through the provider's supported process.
On this page
- Capture the exact hostname and failure
- Inspect the delegation rather than the page
- Compare resolvers without treating one as definitive
- Reconcile the registrar and DNS provider safely
- Verify normal resolution and then the public content
- Check the effect on crawler observations
- Keep a migration record that survives the handoff
- Frequently asked questions
If your website stops resolving after a nameserver change, an old DNSSEC delegation record may no longer match the new provider's signing keys. Compare normal DNS responses with a diagnostic query that disables validation, then reconcile the registrar and authoritative provider configuration. Do not change robots.txt or application redirects to fix a failure that occurs before HTTP begins.
A browser working on one network does not clear the domain. Resolvers can have different cached information, so the same hostname may appear healthy to one visitor and fail for another.
Capture the exact hostname and failure
Record the hostname, migration time, previous DNS provider, and new provider. Check the bare domain and the actual public host separately. A working mail record or another subdomain does not prove the article host resolves.
Use a public hostname you own:
dig @1.1.1.1 www.example.com A +dnssec
dig @1.1.1.1 www.example.com A +dnssec +cdThe second command requests a diagnostic response with validation checking disabled. It is not a recommended permanent resolver setting.
Cloudflare's DNSSEC troubleshooting guide describes this comparison and the common case of changing authoritative providers without updating the old DS record. A normal SERVFAIL alongside a usable diagnostic answer points toward a validation problem worth investigating.
Save the complete responses, including status and authority information. A screenshot saying “site cannot be reached” does not identify whether resolution, TLS, or the application failed.
Inspect the delegation rather than the page
DNSSEC connects information at the parent zone with keys and signatures served by the authoritative zone. The registrar-side DS record and the provider's signing setup must describe the same intended chain.
Check the current nameserver delegation through the registrar and the new provider's documented setup. Then inspect the DS record and the provider's DNSSEC status. Do not copy values from a different zone merely because its dashboard looks similar.
The new provider may show that its zone is active while a cached parent-side record still describes the old keys. These are different observations. Keep both in the incident record.
Avoid making unrelated DNS edits during diagnosis. Changing the A record, proxy state, nameservers, and DS record at once makes it harder to identify what restored service.
The DNS and TLS troubleshooting guide explains the broader connection sequence. Here the specific question is whether validation fails because the delegation and signed zone no longer agree.
Compare resolvers without treating one as definitive
Repeat the same hostname and record type through another trusted resolver. Record the time of each request. Different answers during a migration can reflect cache state rather than random crawler behavior.
Do not conclude that the site is fixed merely because a resolver with validation disabled returns an address. The intended outcome is successful resolution through normal validating paths.
Also check whether the domain points to the expected service after resolution succeeds. A corrected delegation can still lead to an outdated web endpoint. DNS validity and application correctness are separate gates.
A useful worksheet has these columns:
| Observation | What to record |
|---|---|
| Normal query | Resolver, status, answer, time |
| Diagnostic query | Same inputs with checking disabled |
| Parent delegation | Current nameservers and DS information |
| Provider zone | Signing state and supplied setup values |
| Public page | Result after normal resolution works |
This avoids presenting a temporary workaround as a complete repair.
Reconcile the registrar and DNS provider safely
Use the new provider's migration instructions to establish the correct DNSSEC state. Depending on the migration stage, the supported process may involve changing or removing obsolete delegation information before enabling the new chain.
Do not publish a universal command to delete DNSSEC records. The correct sequence depends on the zone, provider, registrar, and cached state. Work from the actual delegation you verified.
Cloudflare's DNSSEC setup guidance discusses nameserver changes and cached DS records. Follow the current instructions for the services you actually use, and retain the previous configuration in the change record.
Keep the work scoped to the affected domain. An account may manage several zones with different providers and signing states.
After applying the documented correction, allow the relevant records to expire according to their actual TTLs. Recheck at meaningful intervals rather than repeatedly switching settings. A clear timeline is more useful than a series of overlapping edits.
Verify normal resolution and then the public content
Once normal queries succeed, fetch the actual article URL without bypassing DNS or certificate checks:
curl -sS -L -D page-headers.txt -o page.html \
'https://www.example.com/guides/setup'Confirm the final URL, expected title, and a distinctive body sentence. Then check the public robots file and sitemap through the same ordinary path.
A successful response from a forced IP address does not establish that the hostname resolves correctly for visitors. Such tests can help isolate layers, but label them as diagnostic evidence.
If resolution is healthy and the page still fails, move to TLS, routing, or application diagnosis. Do not continue changing DNSSEC to solve an unrelated HTTP error.
The status-code guide helps interpret that later stage. Record the transition from DNS failure to a real HTTP response so the team knows which boundary has been repaired.
Check the effect on crawler observations
A failed DNS lookup can prevent a crawler from reaching any page on the host. Server access logs may show no request because the request never arrived.
That absence does not identify which crawler attempted a lookup. Use the operator's available diagnostics and dated observations rather than inventing a visit from an empty log.
After the repair, watch for normal public requests and relevant webmaster updates. A fresh local success does not establish that every resolver has refreshed or that a search system has processed the recovered pages.
For an agency report, state the exact finding: validating DNS responses failed after the provider move, the delegation was corrected, and ordinary resolution plus representative page fetches now work. Avoid promising a traffic recovery date.
Use the migration checklist to include DNS ownership and signing state in future moves.
Keep a migration record that survives the handoff
List the registrar, authoritative provider, domain owner, and DNSSEC maintenance owner. These responsibilities may belong to different people.
Before the next move, record the current delegation and the provider's prescribed sequence. Include a normal validating query and public page fetch in the completion checklist.
Keep email and other domain services in scope for the DNS owner, even if this incident was first noticed through SEO. A web-only screenshot can miss a broader delegation failure.
Test the real production hostname after the change, not only the provider's preview address. Preview access bypasses the very delegation being changed.
A short, accurate record makes the next migration less dependent on someone's memory and gives future investigators a clear baseline.
If the public hostname is an alias, record the target as well as the address eventually returned. A successful lookup for the zone apex does not prove that every name in the alias chain resolves correctly. Test the exact hostname in the failing URL, then inspect any target that fails separately. Keep each observation attached to its hostname so a problem in a dependency is not mistaken for an incorrect web-server rule.
Frequently asked questions
Does SERVFAIL always mean DNSSEC is broken?
No. Use the comparison and delegation evidence to narrow the cause. Other DNS failures can also produce SERVFAIL.
Should I disable validation for visitors?
No. The diagnostic query helps isolate the problem; repair the authoritative configuration so normal validation works.
Can robots.txt fix this failure?
No. The hostname must resolve before a crawler can request robots.txt or any article.
Run the recovered public page through the free Crawlito check after normal DNS resolution is restored.
Filed under Access and robots.txt. Topics: dns, troubleshooting, ai-crawlers