IPv6 issue
Hi,
I’ve noticed that for some domains, I receive a response for dig AAAA from CF, while for others, I do not.
What determines this behavior?
6 Replies
Hi Leo 🙂
I'm trying to understand Cloudflare's behavior, as it responds to IPv6 for some domains but not for others.
are they your domains?
cloudflare has an option to disable ipv6, so the behaviour of not returning AAAA responses would be expected if the owner of the website has done that (as leo correctly said)
a good example of a website with IPv6 disabled is discord.com
Hi Erisa,
Nice to meet you
The option to disable IPv6 in the dashboard only affects the range between cf and the origin servers.
We are looking to disable the previous part of the traffic between the user and the site
I wanted to know if this is something I can configure on the Cloudflare (CF) side, or if it has to be implemented on the development side of the site. Since my client operates with IPv6 on a network that isn’t under CF, we are looking for a more drastic solution.
No,the option to disable IPv6 in the dashboard/api is for communication between user and cloudflare. If you disable IPv6 in the dashboard/api then no AAAA records are returned for proxied records .
We did what you suggested two weeks ago and saw that the requests continued to arrive from certain users on IPv6. Then we contacted CF support and they explained to us that this feature only cancels the requests from CF's side to the servers and not on the part between the user and CF.
They're wrong or we're talking about something different. Could you provide more detail like the domain name and/or screenshot of what you're seeing?
Ticket number might also help, I can't check it because I dont work there but I can pass it on for others to check