IPv6 (AAAA) Record for root domain not working (DNS Only Mode)


Hi, I have an AAAA record (DNS Only Mode) of my root domain pointing to a specific server that we manage but it doesn’t resolve at all and the only IPv6 addresses that we see are the ones Cloudflare has automatically assigned to the root domain.

I believe we should be able to add multiple AAAA addresses for our domain. We don’t need this specific record to be routed to the Cloudflare system so we switched it to DNS only but nothing happens.

Your help is very much appreciated. Thanks!

If you have an A record set to :orange:, I believe custom AAAA entries for that DNS name don’t take effect.

If possible, could you post the domain/subdomain?


Yes indeed my A record goes through the Cloudflare system.
Is there a workaround?

Domain: coders.ph

That DNS entry is set to :orange:

Set your coders.ph AAAA entries all to :grey: and you should see them all show up.

I already did, as stated in my first post. It is already set to “DNS Only”, but nothing happens. I still can’t see my AAAA record propagate.

dig coders.ph AAAA

; <<>> DiG 9.10.6 <<>> coders.ph AAAA

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26326

;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0


;coders.ph. IN AAAA


coders.ph. 196 IN AAAA 2606:4700:30::681c:155b

coders.ph. 196 IN AAAA 2606:4700:30::681c:145b

;; Query time: 2 msec


;; WHEN: Mon Dec 03 01:21:41 PST 2018

;; MSG SIZE rcvd: 83

Do you have any A records for coders.ph that are set to :orange:?

EDIT: Sorry, just caught that you did. @judge already suggested this might be the issue.

I suspect this is intentional behavior by Cloudflare to create a consistent experience across all (AAAA) records for your domain. IPv6 visitors will all be routed through Cloudflare.

1 Like

:wave: @acronix,

You could use a different hostname for your AAAA record. But Cloudflare treats a :grey: AAAA as :orange: if the A record for the same host is :orange: (the reverse is also true).



Thank you guys for the help. Too bad I can’t add AAAA’s for my top-level domain. It could have been very useful for IPv6 virtual host purposes.

If there be any way to request for an exception that would be great.
Otherwise, we’ll just have to live with it and move on.

Oh you can totally add IPv6, Cloudflare will advertise their IPv6 addresses and they will be proxied just like IPv4.

Yes but in this case it is not possible since my A record is :orange: and the AAAA i want to add should be :grey: (for reverse lookup purposes). Cloudflare therefore still treats it as :orange:

And this AAAA record sitting here is basically useless for me.

I don’t want to switch my A to :grey: either since that would be exposing my real ip address.

The only AAAA’s Cloudflare recognizes (for top-level domain) are the ones automatically added by the system (even without adding an AAAA record).

For example, even after removing all the AAAA records in my DNS, I am still getting two AAAA’s by default:

host -t AAAA coders.ph

coders.ph has IPv6 address 2606:4700:30::681c:155b
coders.ph has IPv6 address 2606:4700:30::681c:145b

Adding a new AAAA for my “Top-Level Domain” makes no difference.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.