Hello! I've been using Certbot for a while here cleanly, the past two months or so, but I was having a heap of trouble with my server and memleaks (long story), so I ended up reinstalling Debian 13.
Things were working perfectly before, but now I'm having trouble with obtaining the certificate because of my IPv6 address, which is 2a0f:85c1:356:3522::/64. I can only input it into my registrar as 2a0f:85c1:356:3522::, however. This seemed to work the first time, but the second time around it's causing issues with certbot?
Removing the AAAA records means it will work, but I wanted to check to see if I can fix it w/o just gutting the IPv6 entirely, first. The regular template of information is below, but if you need something else, please let me know.
Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: forgettale.xyz
Type: dns
Detail: DNS problem: NXDOMAIN looking up A for forgettale.xyz - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for forgettale.xyz - check that a DNS record exists for this domain
Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.
My web server is (include version): nginx version: nginx/1.26.3
The operating system my web server runs on is: Debian 13 (Trixie)
With the full IPv6, including the /64, my Registrar's DNS editor refuses to accept it. Also, all ports are open by default (silly, but I was gonna add ufw AFTER i get everything set up, just to make my life with setting up services as easy as pie), so I doubt that's the problem.