When performing domain validation, will the Let’s Encrypt backend support querying servers over IPv6?

Hi all, I just wanted to ask if/suggest that someone is monitoring the logs for http-01 validation to see how frequently one fails with the error "“detail”:"No IPv4 addresses found for ", to help guage the audience that would benefit from this enhancement. Most likely folks who encounter this fail…

Good idea, @FliesLikeABrick . Filed an issue .

Looking forward to IPv6 and Let’s Encrypt compatibility. :slight_smile:

I’d also love to see IPv6-only host support

It’s on the upcoming features with a ETA set to tomorrow.

How about adding an IPv6-in-IPv4 tunnel or a vpn service that can assign IPv6 address on the edge server (or a trusted external server that has dual-stack addresses)？ When the v6-in-v4 tunnel or vpn connection is established between the real server and the edge server, the real server will have IPv6…

Now it states ETA: Before April 22, 2016 -> today :slight_smile: Looking forward. It can only be a matter of days… Thank you so much for all the work!

Still not working whit ipv6 only domains

For those intending to actually test the functionality, please subscribe to the GitHub issue here instead of posting complaints or requesting updates.

Support for IPv6-only hosts

Issuance Tech

Topic		Replies	Views
403 Forbidden when trying to generate new LetsEncrypt cert Help	9	4524	November 30, 2020
Server with IPv6 AAAA record only Help	20	7593	March 11, 2021
Problems validating IPv6 against host running 6to4 Help	10	3580	August 1, 2016
Unable to request cert due to IPv6 issue Help	11	798	April 6, 2021
HTTP validation failures due to timeout (IPv6 issues maybe?) Client dev	15	3446	August 3, 2017

Support for IPv6-only hosts

Related topics