Ipv6 only acme issues

Apparently, it is impossible to generate a TLS cert for an IPv6-only domain.

My domain is: 0000d267d199c1653868.home.daniil.it

I ran this command:
caddy with a basic Caddyfile containing only 0000d267d199c1653868.home.daniil.it

It produced this output:

Activating privacy features... 2019/09/23 14:05:35 [INFO] [0000d267d199c1653868.home.daniil.it] acme: Obtaining bundled SAN certificate
2019/09/23 14:05:36 [INFO] [0000d267d199c1653868.home.daniil.it] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz-v3/469039540
2019/09/23 14:05:36 [INFO] [0000d267d199c1653868.home.daniil.it] acme: use tls-alpn-01 solver
2019/09/23 14:05:36 [INFO] [0000d267d199c1653868.home.daniil.it] acme: Trying to solve TLS-ALPN-01
2019/09/23 14:05:43 [0000d267d199c1653868.home.daniil.it] failed to obtain certificate: acme: Error -> One or more domains had a problem:
[0000d267d199c1653868.home.daniil.it] acme: error: 400 :: urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up A for 0000d267d199c1653868.home.daniil.it, url:

My web server is (include version): Caddy 1.0.0-beta1

The operating system my web server runs on is (include version): Arch linux

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don’t know): yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):

Hi @danog, welcome to the community forum.

It sounds like this has been your experience so far but it isn’t true. It’s definitely possible to do this though some ACME clients/configurations may handle it better than others.

I’m able to reproduce the NXDOMAIN result that Caddy reported in the problem message: https://unboundtest.com/m/AAAA/0000d267d199c1653868.home.daniil.it/H2GF6Y3Z

There are also a number of errors reported by DNSViz: http://dnsviz.net/d/home.daniil.it/dnssec/

It appears to me that the problems you’re experiencing are related to your authoritative DNS configuration and not particular to IPv6.

1 Like

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