DNS not updating for over 24 hours

[jesse13]

What is the name of the domain?

archival.dev

What is the issue you’re encountering

DNS no longer updates, stale values are stuck for over 24 hours and new records also don’t show up.

What steps have you taken to resolve the issue?

I’ve tried turning proxy on and off, clearing various caches, and verifying through multiple tools including cloudflare’s own resolver (1.1.1.1 DoH JSON API).
I expect (as shown in the screenshot) at least 5 CNAMEs and 4 TXT records, instead I see 0 CNAMEs and 2 TXT records.

What feature, service or problem is this related to?

DNS not responding/updating

What are the steps to reproduce the issue?

If you run curl -H "accept: application/dns-json" "https://cloudflare-dns.com/dns-query?name=archival.dev&type=TXT"

{"Status":0,"TC":false,"RD":true,"RA":true,"AD":true,"CD":false,"Question":[{"name":"archival.dev","type":16}],"Answer":[{"name":"archival.dev","type":16,"TTL":300,"data":"\"v=spf1 include:_spf.google.com -all\""},{"name":"archival.dev","type":16,"TTL":300,"data":"\"google-site-verification=_syHCF1IIMriwn9tQqUKnjJADcyMm3CTjH5S3U7ppcs\""}]}

CNAME doesn’t even have an Answer field curl -H "accept: application/dns-json" "https://cloudflare-dns.com/dns-query?name=archival.dev&type=CNAME"

{"Status":0,"TC":false,"RD":true,"RA":true,"AD":true,"CD":false,"Question":[{"name":"archival.dev","type":5}],"Authority":[{"name":"archival.dev","type":6,"TTL":1435,"data":"lara.ns.cloudflare.com. dns.cloudflare.com. 2345451669 10000 2400 604800 1800"}]}

The screenshot shows the expected values.

Screenshot of the error

[jesse13]

Possible helpful things to note:

• I accidentally deleted this domain from cloudflare a few days ago and re-added it.
• I enabled DNSSEC via CF and my registrar to see if that would trigger a configuration update, no joy.
• Querying subdomains results in the same thing.
• Old records continue to work. In the screenshot, the R2 URLs are old and appear to continue to work. editor CNAME also appears to resolve but it could be a local cache. I have cleared my machine’s cache If I query for this CNAME I receive no response.
• New records (e.g. the apex record, www, test, and opc) don’t show up.

I’m not sure I’m totally understanding how CNAME lookups should work, but at minimum I’m missing a few TXT records and the DNS is still resolving to the wrong URL or 522ing, depending on if it’s old or new.

What is the expected functionality here and is it possible for someone to trigger a cache bust? This is really slowing me down, I was hoping to launch this service this week but if the domain doesn’t resolve I can’t go live

[jesse13]

To repro a 522, visit www.archival.dev

[cscharff]

The TxT records resolve correctly based on you screenshot.

The CNAME doesn’t have an answer for 2 reasons. A CNAME is illegal for the domain root record so Cloudflare will flatten it to an A record. It is also proxied so Cloudflare would have returned an A record even if it were allowed.

Queries for the other records need to be specific to the record being queried. And again proxied records return a A record for Cloudflare’s edge.

Follow the linked article to 522 for troubleshooting steps for that error message.

[jesse13]

Ah, got it - so to recap:

• CNAMEs that are proxied will show up as A records when doing dns queries, I’ll need to line up the IPs to check if one domain is pointed at another.
• I should expect non-proxied CNAMEs to show up via my queries, but I have none.
• 522 is a different issue, likely due to configuration on my end.
• TXT records that are actually set on the apex show up when querying, the ones set on subdomains will show up when querying those subdomains explicitly but not at the root.

I think I mostly wasn’t understanding the proxying behavior, the others seem obvious in retrospect.

Thanks!