DNS Verification Issues

DNS Verification Issues

Domain stuck as "unverified"

A domain must prove DNS control before any checks run against it:

1. Click "How to verify" on the domain to get a TXT record name (_yadt-verify.<domain>) and a token value. Before v0.2.4 the record was called _dmarc-dashboard-verify.<domain>; a domain that's still pending with that record verifies too, and verified domains are never re-checked, so an old record can simply be deleted.
2. Publish that TXT record in the domain's real DNS.
3. Click "Check now" — once the record resolves, the domain flips to verified and checks start running (see How DNS Checks Are Scheduled).

If "Check now" still reports the record missing after you've published it: give DNS propagation time (a few minutes to a few hours depending on your DNS host and any existing TTL on that name), then confirm the record is actually visible with a direct lookup, e.g. dig TXT _yadt-verify.yourdomain.com — if that returns nothing, the record wasn't published where the domain's authoritative nameservers actually are (a common mistake: publishing at the registrar's default parking DNS instead of the zone actually serving the domain).

Subdomain shows as unverified even though the parent domain is verified

This should be automatic — a subdomain of an already-verified apex domain inherits verification without its own token. If it isn't inheriting, check that the apex domain (not an intermediate subdomain) is the one marked verified, since inheritance walks from the exact registered parent.

---

← Troubleshooting & FAQ · Home