The lovely new CT logs currently only support IPv4:
oak.ct.letsencrypt.org. 59 A 220.127.116.11 oak.ct.letsencrypt.org. 59 A 18.104.22.168 oak.ct.letsencrypt.org. 59 A 22.214.171.124 testflume.ct.letsencrypt.org. 59 A 126.96.36.199 testflume.ct.letsencrypt.org. 59 A 188.8.131.52 testflume.ct.letsencrypt.org. 59 A 184.108.40.206
Can you add IPv6 support?
I’m only asking because I always promote IPv6, and everything else you run is dual-stack. I don’t have any sort of specific problem.
Assuming they’re running on ELBs, it should be as simple as adding
ALIAS records, and/or switching to the
dualstack ELB hostnames. (I’m kind of guessing, since I’ve never done it.) Enabling IPv6 should reduce your Route 53 bills, since
ALIAS responses are free but
NODATA responses are charged.
Of course, enabling things is simpler than solving other issues like monitoring or software support.