Retour au centre d'aide

Centre d'aide

My domain is stuck on "Verifying DNS"

Why DNS verification fails or stalls, and how to fix the most common causes yourself before contacting support.

How long it should take

For most domains: under 5 minutes. We re-check DNS every 5 minutes for the first 24 hours.

For some registrars or ccTLDs (.com.mx, .com.br, .in, .de): up to a few hours while DNS caches refresh worldwide.

Run the checks yourself

Open a terminal and run:

dig +short _zebrasnap-verify.your-domain.com TXT
dig +short your-domain.com A           # or CNAME for a subdomain

You should see the values you added. If you see nothing, the records didn't save at your registrar. If you see a different value, look at the record at your registrar — the value field probably has a typo or extra quotes.

Common gotchas

  • Cloudflare proxy on. Cloudflare's orange-cloud proxy hides your real DNS during verification. Set the A record to "DNS only" (gray cloud) until your domain is live.
  • TXT name doubled. Some registrars auto-append the domain. If you typed _zebrasnap-verify.yourname.com and your registrar already adds .yourname.com, the resulting record is _zebrasnap-verify.yourname.com.yourname.com. Use just _zebrasnap-verify as the name.
  • @ vs full apex. For the A record at the apex, Namecheap and GoDaddy use @. Cloudflare uses the full domain name. Either way, the resulting record is yourname.com → IP.
  • Wrong IP. Re-copy the IP from the settings page. We update it occasionally.
  • www. not added. Without the www CNAME, www.yourname.com will fail to load even though yourname.com works.

Still stuck after 24 hours?

We send you an email at the 24-hour mark with a checklist tailored to what we observed. If you still can't get past it, open the contact form — DNS issues are technical and we're happy to walk through it with you.