AAAA (IPv6) record for apex domains?


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.

Thank you!

Hey @SmashManiac,

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 URL. Otherwise, you’ll need an A record pointed at the Netlify load balancer. All of this is documented above :arrow_double_up:.

Once propagated, you’ll be good to go.

I already have this configuration set up, but online IPv6 site valdators are failing because of the missing AAAA record.

As I mentioned in my original post, said guide does not specify the AAAA record, only the A record, hence why I’m asking for support.

Hey @SmashManiac,

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!

1 Like

I just found an IPv6 adoption chart for Google services, for reference. As of this writing, it currently is at about 33%.

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 :slight_smile:

1 Like