- Edited
I set up everything but unbound fail to dns resolution I already spent a day reading others discussion related to that but my knowleddge limited to conclu a solution BTW IM using a ec2 instance from aws and I opened all port
admin@ip-172-31-23-160:/opt/mailcow-dockerized$ sudo docker compose logs unbound-mailcow
unbound-mailcow-1 | Setting console permissions…
unbound-mailcow-1 | Receiving anchor key…
unbound-mailcow-1 | Receiving root hints…
######################################################################## 100.0%
unbound-mailcow-1 | setup in directory /etc/unbound
unbound-mailcow-1 | Certificate request self-signature ok
unbound-mailcow-1 | subject=CN=unbound-control
unbound-mailcow-1 | removing artifacts
unbound-mailcow-1 | Setup success. Certificates created. Enable in unbound.conf file to use
unbound-mailcow-1 | 2024-10-01 13:23:13,520 INFO Set uid to user 0 succeeded
unbound-mailcow-1 | 2024-10-01 13:23:13,531 INFO supervisord started with pid 1
unbound-mailcow-1 | 2024-10-01 13:23:14,536 INFO spawned: ‘processes’ with pid 22
unbound-mailcow-1 | 2024-10-01 13:23:14,540 INFO spawned: ‘syslog-ng’ with pid 23
unbound-mailcow-1 | 2024-10-01 13:23:14,549 INFO spawned: ‘unbound’ with pid 24
unbound-mailcow-1 | 2024-10-01 13:23:14,552 INFO spawned: ‘unbound-healthcheck’ with pid 25
unbound-mailcow-1 | [1727788994] unbound[24:0] notice: init module 0: validator
unbound-mailcow-1 | [1727788994] unbound[24:0] notice: init module 1: iterator
unbound-mailcow-1 | Oct 1 13:23:14 cab1da3c6ff2 syslog-ng[23]: syslog-ng starting up; version=‘4.7.1’
unbound-mailcow-1 | [1727788994] unbound[24:0] info: start of service (unbound 1.20.0).
unbound-mailcow-1 | 2024-10-01 13:23:15,696 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
unbound-mailcow-1 | 2024-10-01 13:23:15,696 INFO success: syslog-ng entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
unbound-mailcow-1 | 2024-10-01 13:23:15,696 INFO success: unbound entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
unbound-mailcow-1 | 2024-10-01 13:23:15,696 INFO success: unbound-healthcheck entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
unbound-mailcow-1 | [1727788999] unbound[24:0] info: generate keytag query _ta-4f66. NULL IN
unbound-mailcow-1 | [1727788999] unbound[24:0] info: failed to prime trust anchor – DNSKEY rrset is not secure . DNSKEY IN
unbound-mailcow-1 | [1727788999] unbound[24:0] info: generate keytag query _ta-4f66. NULL IN
unbound-mailcow-1 | [1727788999] unbound[24:0] info: failed to prime trust anchor – DNSKEY rrset is not secure . DNSKEY IN
unbound-mailcow-1 | [1727788999] unbound[24:0] info: generate keytag query _ta-4f66. NULL IN
unbound-mailcow-1 | [1727788999] unbound[24:0] info: failed to prime trust anchor – DNSKEY rrset is not secure . DNSKEY IN
unbound-mailcow-1 | [1727788999] unbound[24:0] info: generate keytag query _ta-4f66. NULL IN
unbound-mailcow-1 | [1727788999] unbound[24:0] info: failed to prime trust anchor – DNSKEY rrset is not secure . DNSKEY IN
unbound-mailcow-1 | [1727788999] unbound[24:0] info: generate keytag query _ta-4f66. NULL IN
unbound-mailcow-1 | [1727788999] unbound[24:0] info: failed to prime trust anchor – DNSKEY rrset is not secure . DNSKEY IN
unbound-mailcow-1 | [1727788999] unbound[24:0] info: failed to prime trust anchor – DNSKEY rrset is not secure . DNSKEY IN
unbound-mailcow-1 | [1727788999] unbound[24:0] info: generate keytag query _ta-4f66. NULL IN
unbound-mailcow-1 | [1727788999] unbound[24:0] info: failed to prime trust anchor – DNSKEY rrset is not secure . DNSKEY IN
unbound-mailcow-1 | [1727788999] unbound[24:0] info: failed to prime trust anchor – DNSKEY rrset is not secure . DNSKEY IN
unbound-mailcow-1 | 2024-10-01 13:23:20: Healthcheck: DNS Resolution Failed on attempt 1 for fuzzy.mailcow.email! Trying again…
unbound-mailcow-1 | 2024-10-01 13:23:20: Healthcheck: DNS Resolution Failed on attempt 2 for fuzzy.mailcow.email! Trying again…
unbound-mailcow-1 | 2024-10-01 13:23:20: Healthcheck: DNS Resolution Failed on attempt 3 for fuzzy.mailcow.email! Trying again…
unbound-mailcow-1 | 2024-10-01 13:23:20: Healthcheck: DNS Resolution not possible after 3 attempts for fuzzy.mailcow.email… Gave up!
unbound-mailcow-1 | 2024-10-01 13:23:20: Healthcheck: DNS Resolution Failed on attempt 1 for github.com! Trying again…
unbound-mailcow-1 | 2024-10-01 13:23:20: Healthcheck: DNS Resolution Failed on attempt 2 for github.com! Trying again…
unbound-mailcow-1 | 2024-10-01 13:23:20: Healthcheck: DNS Resolution Failed on attempt 3 for github.com! Trying again…
unbound-mailcow-1 | 2024-10-01 13:23:20: Healthcheck: DNS Resolution not possible after 3 attempts for github.com… Gave up!
unbound-mailcow-1 | 2024-10-01 13:23:20: Healthcheck: DNS Resolution Failed on attempt 1 for hub.docker.com! Trying again…
unbound-mailcow-1 | 2024-10-01 13:23:20: Healthcheck: DNS Resolution Failed on attempt 2 for hub.docker.com! Trying again…
unbound-mailcow-1 | 2024-10-01 13:23:20: Healthcheck: DNS Resolution Failed on attempt 3 for hub.docker.com! Trying again…
unbound-mailcow-1 | 2024-10-01 13:23:20: Healthcheck: DNS Resolution not possible after 3 attempts for hub.docker.com… Gave up!
unbound-mailcow-1 | 2024-10-01 13:23:20: Healthcheck: Too many DNS failures (1 failures allowed, you got 3 failures), marking Healthcheck as unhealthy…
unbound-mailcow-1 | 2024-10-01 13:23:56: Healthcheck: DNS Resolution Failed on attempt 1 for fuzzy.mailcow.email! Trying again…
unbound-mailcow-1 | 2024-10-01 13:23:56: Healthcheck: DNS Resolution Failed on attempt 2 for fuzzy.mailcow.email! Trying again…
unbound-mailcow-1 | 2024-10-01 13:23:56: Healthcheck: DNS Resolution Failed on attempt 3 for fuzzy.mailcow.email! Trying again…
unbound-mailcow-1 | 2024-10-01 13:23:56: Healthcheck: DNS Resolution not possible after 3 attempts for fuzzy.mailcow.email… Gave up!
unbound-mailcow-1 | 2024-10-01 13:23:57: Healthcheck: DNS Resolution Failed on attempt 1 for github.com! Trying again…
unbound-mailcow-1 | 2024-10-01 13:23:57: Healthcheck: DNS Resolution Failed on attempt
IM here if you need more informations
if youned more information im here