The documentation about how to set up Netlify for an external DNS server specifies the A record to set up for apex domains, but not the AAAA record. However, I just noticed that my Netlify subdomain does have an AAAA record, so that omission seems strange to me.
My understanding is that because of this, users of my website won’t be able to access it using IPv6 from apex, even though Netlify sites appears to support this protocol. Note that my registrar does not support CNAME-like flattening, so I cannot use that workaround.
As such, I was wondering what AAAA record I should put in, and if it could possibly be added to Netlify Docs. If such a feature does not exist, I would appreciate if a mod could convert this topic into a feature request.
You’re looking to make sure that your apex domain (non-www) can be accessed over IPv6, correct?
The following guide outlines what you can do to make this work, whether your registrar supports special record types or not:
If they do, great! Point the CNAME/ANAME/ALIAS record at your .netlify.com URL. Otherwise, you’ll need an A record pointed at the Netlify load balancer. All of this is documented above .
So long as your apex domain is pointing at us through either an A record or CNAME/ANAME/ALIAS as above, we will perform the necessary redirect.
Validators will probably fail because, as you know, they’ll be looking for the AAAA record. This is only a necessity, as far as I’m aware, on an end-to-end IPv6 lookup (which don’t occur at the moment, again, as far as I’m aware).
This said, as per your original post, I’ve added this discussion to our open feature request!
Also, I recently learned that some ISPs (in India for example) have been forced for a few years now to sell IPv6 connections to customers due to IPv4 address shortage, but I’m not sure if they all use a transition technology to compensate or not, so I don’t know how much of an issue this currently is.
They certainly do use a translation technology - there are quite a few internet services (such as all google TCP load balancer customers, like us) that cannot support ipv6 yet.
So - it’s something we are interested in, but we need all of our service providers to catch up to be able to do so
With 45% of our traffic coming over IPv6, it’s quite disappointing that Netlify doesn’t support IPv6 for apex domains in 2021 unless we delegate it to Netlify DNS - which we can’t do, because we have to maintain our own zone - and even if we could, there is no Terraform provider for it, so it’s pretty much unmanageable.
Is there a roadmap or timing on when IPv6 will be available for the apex domain to point to the load balancer? I have a number of clients whose governance models do not allow for us to utilize Netlify DNS, but who are asking questions about IPv6 support.
May 2024 and this thread is the first result on Google when searching for Netlify and ipv6. Is this still unsupported with no plans to support it? Especially with AWS becoming more ipv6 centric, ipv6 lookups are becoming more and more common.
Yea, I don’t want to use Netlify DNS, and for some projects, specifically cannot. This is becoming crippling as more services move to support ipv6. Again, it’s 2024.
.
