Cloudflare continues to serve AAAA records for my domain, even though I’ve removed them from my DNS dashboard. I’m trying to connect my site to an external platform that requires zero AAAA records, but external DNS tools are still showing IPv6 addresses, which appear to be Cloudflare-owned and injected automatically. I suspect this is related to CNAME flattening at the root domain, even though the record is set to DNS only.
What steps have you taken to resolve the issue?
Removed all visible AAAA records
Set the CNAME for the root domain to DNS only (grey cloud)
Purged cache
Flushed local DNS
Enabled development mode
Waited over 48 hours
Verified externally that no AAAA records exist in the dashboard
Added and deleted dummy records to try to force cache refresh
Read similar issues in this forum with unresolved DNS caching after flattening
What feature, service or problem is this related to?
There are no AAAA records in my Cloudflare DNS dashboard
I’ve purged cache, flushed DNS, and waited 48+ hours
But AAAA records are still being served when I check externally via DNS tools (showing Cloudflare IPv6 addresses).
Would appreciate any help confirming if Cloudflare could be injecting these even with proxying disabled — or how to prevent them from being served entirely.
There are 2 sets of Cloudflare nameservers resolving for your domain and the apex record is returning proxied which doesn’t match what you have set, so likely you are not in the Cloudflare account where the domain is active… https://cf.sjr.dev/tools/check?da5c7a90b08a4ddabdde6f287210a449#dns
If unsure, can you show a screenshot of your whole DNS page, including the nameservers at the bottom and the bar at the top that looks like this…
I just wanted to check — is this truly the only option available?
I’m a Pro Plan customer, and I’ve really tried to do all the right things to resolve this issue myself. Unfortunately, I’ve been sent in circles trying to access actual support.
Every time I try to open a support ticket, I get this error:
pgsql
CopyEdit
No contact found for federation identifier: 79606736
I’ve tried everything: incognito, clearing cache, direct links — nothing is working.
Could a moderator or Cloudflare staff member please confirm if there’s any other possible way to:
You are in the correct account however the CNAME target sites.ludicrous.cloud has AAAA records so you can’t do anything to stop that.
Go High Level give an A record instead to use for the apex domain here, so use that if you need to validate your DNS settings…
Once validated, you may be able to switch back to the CNAME and then proxy it to take advantage of O2O. Otherwise you may be better to use it through a subdomain like www…
Thanks so much for the clarification — that definitely helps me understand what’s going on with the CNAME flattening and the FRUSTRATING and persistent AAAA records.
I’ve reached out to Innovorise (the platform I’m connecting my domain to) to see if they can provide an A record instead, or confirm whether they support subdomain routing or O2O proxying.
That said, I’m not that happy with the runaround in trying to seek support from Cloudflare as a paid user due to the federation ID error (No contact found for federation identifier: 79606736). So if there’s anything else Cloudflare staff can offer here — or a way to escalate this — I’d really appreciate it.
Thanks again to everyone who’s replied and helped so far- at least I can see a way forward
I’m not sure who Innovorise are, Google doesn’t show anything, but sites.ludicrous.cloud is Go High Level’s Cloudflare-for-SaaS customer domain and they give the A record to use in the document I linked to, although the CNAME is needed to use O2O.
