i solve this error seting my dns on extra compose file for each container like doc say:
`version: ‘2.1’
services:
ipv6nat-mailcow:
image: bash:latest
restart: “no”
entrypoint: [“echo”, “ipv6nat disabled in compose.override.yml”]
clamd-mailcow:
dns:
- my_ip_dns_fw
rspamd-mailcow:
dns:
- my_ip_dns_fw
php-fpm-mailcow:
dns:
- my_ip_dns_fw
sogo-mailcow:
dns:
- my_ip_dns_fw
dovecot-mailcow:
dns:
- my_ip_dns_fw
postfix-mailcow:
dns:
- my_ip_dns_fw
nginx-mailcow:
dns:
- my_ip_dns_fw
acme-mailcow:
dns:
- my_ip_dns_fw
watchdog-mailcow:
environment:
- CHECK_UNBOUND=0
dns:
- my_ip_dns_fw
dockerapi-mailcow:
dns:
- my_ip_dns_fw
`
and same on unbound to forward queries to the same my_ip_dns_fw…. i notice this because have 3 deployments , on one of them i see the correct record dns… so made the changes restart ct and everything ok .. maybe is too late to say on 2024 lol