Vercel DNS UI/CLI accepts these records, but authoritative DNS does not serve them:
_dmarc TXT "v=DMARC1; p=none;" default._bimi TXT "v=BIMI1; l= https://wearjoyous.com/bimi/joyous-logo.svg; "
Why do these accepted records do not resolve from ns1.vercel-dns.com / ns2.vercel-dns.com?
Shopify CNAME records resolve correctly, and other underscore TXT records resolve correctly, so this appears specific to these owner names.
Hi Daniel,
I’d first verify the exact owner names being created in the Vercel DNS zone.
If the DNS zone is wearjoyous.com, the record Name fields should usually be:
_dmarcdefault._bimi
not the full hostname, unless the UI/CLI specifically expects the full name.
The final records should resolve as:
_dmarc.wearjoyous.comdefault._bimi.wearjoyous.com
I’d query Vercel’s authoritative nameservers directly, bypassing resolver/cache issues:
dig NS wearjoyous.com +short
dig TXT _dmarc.wearjoyous.com @ns1.vercel-dns.com +shortdig TXT _dmarc.wearjoyous.com @ns2.vercel-dns.com +short
dig TXT default._bimi.wearjoyous.com @ns1.vercel-dns.com +shortdig TXT default._bimi.wearjoyous.com @ns2.vercel-dns.com +short
If dig NS does not show Vercel nameservers, then the records may exist in Vercel’s DNS UI but they are not the authoritative records used by the internet.
If dig NS does show Vercel nameservers and both @ns1 / @ns2 still return nothing, I’d delete and recreate one of the TXT records using only the short name, for example _dmarc, then test that one again after a few minutes.
For the BIMI value, I’d also remove extra spaces around the URL/semicolon while testing:
v=BIMI1; l=https://wearjoyous.com/bimi/joyous-logo.svg;
If the recreated record appears in the Vercel dashboard but still does not answer from ns1.vercel-dns.com or ns2.vercel-dns.com, then that is good evidence that the DNS zone is not being served correctly and would need Vercel-side investigation.