Is it possible to get more detailed logs from unbound-mailcow?
All I currently see through ‘docker compose logs unbound-mailcow’ are the startup logs.
Every couple of days, acme-mailcow appears to fail to resolve the A record of one of my mail servers and then proceeds to generate a certificate excluding it. At the next run, the record is found and the certificate is regenerated to include it.
The domain is present in 3 geographically dispersed nameservers.
Both the autodiscover and autoconfig A records for the same domain are found successfully, so I suspect it might be a lookup timeout issue since the A record for the mail server is looked up first.
Since unbound is the nameserver on the client side, I’m assuming that acme-mailcow consults it and that it is the component that is failing to resolve the A record for the mail server. If I’m wrong, please point me in the right direction.
acme-mailcow-1 | Sat Jul 6 15:23:42 CAT 2024 - No A or AAAA record found for hostname mail.mydomain.com
acme-mailcow-1 | Sat Jul 6 15:23:42 CAT 2024 - Found A record for autodiscover.mydomain.com: xxx.xxx.xxx.xxx
acme-mailcow-1 | Sat Jul 6 15:23:42 CAT 2024 - Confirmed A record xxx.xxx.xxx.xxx
acme-mailcow-1 | Sat Jul 6 15:23:42 CAT 2024 - Found A record for autoconfig.mydomain.com: xxx.xxx.xxx.xxx
acme-mailcow-1 | Sat Jul 6 15:23:42 CAT 2024 - Confirmed A record xxx.xxx.xxx.xxx
acme-mailcow-1 | Sun Jul 7 15:26:38 CAT 2024 - Found A record for mail.mydomain.com: xxx.xxx.xxx.xxx
acme-mailcow-1 | Sun Jul 7 15:26:38 CAT 2024 - Confirmed A record xxx.xxx.xxx.xxx
acme-mailcow-1 | Sun Jul 7 15:26:38 CAT 2024 - Found A record for autodiscover.mydomain.com: xxx.xxx.xxx.xxx
acme-mailcow-1 | Sun Jul 7 15:26:38 CAT 2024 - Confirmed A record xxx.xxx.xxx.xxx
acme-mailcow-1 | Sun Jul 7 15:26:38 CAT 2024 - Found A record for autoconfig.mydomain.com: xxx.xxx.xxx.xxx
acme-mailcow-1 | Sun Jul 7 15:26:38 CAT 2024 - Confirmed A record xxx.xxx.xxx.xxx
Thanks