bug: unbound container failing to resolve mailcow.email and other domains about mailcow-dockerized HOT 2 CLOSED

There seems to be a number of hosts unbound is not resolving. I found

Logs for the dovecot container showed that www.spamassassin.heinlein-support.de was not being resolved.

mail:~#docker exec -it mailcowdockerized-unbound-mailcow-1 bash
18b739925f75:/# host www.spamassassin.heinlein-support.de 127.0.0.1
;; communications error to 127.0.0.1#53: timed out
;; communications error to 127.0.0.1#53: timed out
;; no servers could be reached

18b739925f75:/# host www.spamassassin.heinlein-support.de 1.1.1.1
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases: 

www.spamassassin.heinlein-support.de has address 185.97.174.62
18b739925f75:/# host www.spamassassin.heinlein-support.de 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases: 

www.spamassassin.heinlein-support.de has address 185.97.174.62

from mailcow-dockerized.

SOLVED!

Our upstream provider was blocking IPS from www.ipdeny.com. This was causing unbound to not be able to hit root dns servers and for dovecot to not be able to connect to www.spamassassin.heinlein-support.de which causes it to not start properly.

This caused mailcow to reset the 993 connection attempt, which is what lead me down this road originally.

Long story short, if you are getting dovecot container reseting connection attempts to its ports (993,995,110,143) and/or unbound is not resolving random hostnames, check that your ip connections are not being blocked up stream.

They removed the blocks and evrything is working perfectly now.

from mailcow-dockerized.