I have a strange behaviour of the ACME client:
FQDN of my mailserver is cloudmail.example1.de with a valid A- and AAAA-record.
There are several DNS-Aliases pointing to the main-record like:
After the latest update of Ubuntu last days and checking/renewing the certificate the server tells me now that the AAAA-record does not fit the local IP(v6) address and that he want to skip the main FQDN.
What is very interesting is that all the aliases (pointing the main FQDN) works and now I have a newly issued certificate for autoconfig.example2.de.
Sooner or later I expact problems while delivering mails because the main FQDN is not named in the certificate anymore …
Here are the logs from ACME client (via webUI):
cloudmail.example1.de - Cannot match your IP 2001:xxxx:xxxx:xxxx::1 against hostname cloudmail.example1.de (DNS returned fd4d:xxxx:xxxx:xxxx:0000:0000:0000:0003)
What is interesting is that the second named IP (fd4d:….) matches the IP-subnet of the br-mailcow interface at the server.
I already deleted the docker containers and recreated them …
Any ideas? Thanks for your help and merry xmas - happy holidays!