Introduction

A domain verification request that stays pending after a DNS change usually means the verifying service still cannot see the exact record it expects. The dashboard may say the record exists, but that does not prove the public authoritative answer is correct. The fix is to validate the active DNS response from the outside and make sure the record lives on the right hostname, in the right zone, without being masked by the migration.

Symptoms

  • A provider keeps showing domain verification as pending after DNS updates
  • The verification TXT record appears in the DNS dashboard but is not accepted
  • Verification worked before a nameserver or DNS provider change and now fails
  • Different DNS lookup tools show different answers or no answer at all
  • The issue affects one hostname or subdomain more than the root domain

Common Causes

  • The verification TXT record was added to the wrong hostname or wrong DNS zone
  • Authoritative nameservers still serve old data after the DNS migration
  • The domain is delegated incorrectly and the verifying service queries a different zone than expected
  • Multiple TXT records or stale provider records make the verification ambiguous
  • Proxy or platform-specific DNS behavior hides the effective record placement during migration

Step-by-Step Fix

  1. Check the exact hostname and record value the provider expects, including whether it belongs at the root, a subdomain, or a provider-specific label.
  2. Query the record against the authoritative nameservers directly so you can see the true public answer instead of trusting the dashboard alone.
  3. Verify that the domain now delegates fully to the intended DNS provider and no old nameserver set still serves competing answers.
  4. Review TXT records on the same name for duplicates, truncation, or formatting issues that could confuse the verifying service.
  5. If the domain recently moved providers, confirm the verification record was recreated in the new zone rather than only left behind in the old one.
  6. Wait for TTL expiry only after the authoritative answer is correct on every nameserver.
  7. Retry verification once public lookups consistently show the expected value from outside your network.
  8. If the hostname is proxied or managed through a platform, confirm that the verification method is compatible with that platform's DNS behavior.
  9. Keep provider-verification records documented during DNS migrations so external services do not lose trust unexpectedly.