Based on
I would guess that either your IPv6 address (AAAA record in your DNS) does not point to the same server as your IPv4 address (A record in your DNS) or that your webserver configuration does not respond to requests over IPv6, which Let's Encrypt uses by default. If it won't harm any of your operations, you could simply try removing your AAAA record then attempting the certbot dry run again.