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

    Have something to say?

    Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

    esackbauer it healthy I had to add forward zone and restart then u -d .
    but I have a problem cnat send message sogo says sent but it didint
    postfix-mailcow-1 | No SPAMHAUS_DQS_KEY found… Skipping Spamhaus blocklists entirely!
    postfix-mailcow-1 | 2024-10-01 14:48:04,026 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    postfix-mailcow-1 | 2024-10-01 14:48:04,026 INFO success: postfix entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    postfix-mailcow-1 | 2024-10-01 14:48:04,026 INFO success: syslog-ng entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    postfix-mailcow-1 | chown: cannot access ‘/usr/share/man/man1/mailq.1.gz’: No such file or directory
    postfix-mailcow-1 | Oct 1 14:48:06 ae0ccdcc0a15 postfix/postfix-script[337]: starting the Postfix mail system
    postfix-mailcow-1 | Oct 1 14:48:06 ae0ccdcc0a15 postfix/master[339]: daemon started – version 3.7.11, configuration /opt/postfix/conf
    postfix-mailcow-1 | Oct 1 14:48:10 ae0ccdcc0a15 postfix/postscreen[345]: cache proxy:btree:/var/lib/postfix/postscreen_cache full cleanup: retained=0 dropped=0 entries
    postfix-mailcow-1 | Oct 1 14:48:10 ae0ccdcc0a15 postfix/postscreen[345]: CONNECT from [172.22.1.12]:34563 to [172.22.1.253]:25
    postfix-mailcow-1 | Oct 1 14:48:10 ae0ccdcc0a15 postfix/postscreen[345]: ALLOWLISTED [172.22.1.12]:34563
    postfix-mailcow-1 | Oct 1 14:48:10 ae0ccdcc0a15 postfix/smtpd[347]: connect from mailcowdockerized-acme-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.12]
    postfix-mailcow-1 | Oct 1 14:48:10 ae0ccdcc0a15 postfix/smtpd[347]: lost connection after CONNECT from mailcowdockerized-acme-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.12]
    postfix-mailcow-1 | Oct 1 14:48:10 ae0ccdcc0a15 postfix/smtpd[347]: disconnect from mailcowdockerized-acme-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.12] commands=0/0
    postfix-mailcow-1 | Oct 1 14:48:10 ae0ccdcc0a15 postfix/postscreen[345]: CONNECT from [172.22.1.12]:37376 to [172.22.1.253]:25
    postfix-mailcow-1 | Oct 1 14:48:10 ae0ccdcc0a15 postfix/postscreen[345]: ALLOWLISTED [172.22.1.12]:37376
    postfix-mailcow-1 | Oct 1 14:48:10 ae0ccdcc0a15 postfix/smtpd[347]: connect from mailcowdockerized-acme-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.12]
    postfix-mailcow-1 | Oct 1 14:48:10 ae0ccdcc0a15 postfix/smtpd[347]: Anonymous TLS connection established from mailcowdockerized-acme-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.12]: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256
    postfix-mailcow-1 | Oct 1 14:48:10 ae0ccdcc0a15 postfix/smtpd[347]: lost connection after STARTTLS from mailcowdockerized-acme-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.12]
    postfix-mailcow-1 | Oct 1 14:48:10 ae0ccdcc0a15 postfix/smtpd[347]: disconnect from mailcowdockerized-acme-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.12] ehlo=1 starttls=1 commands=2
    postfix-mailcow-1 | Oct 1 14:52:24 ae0ccdcc0a15 postfix/sogo/smtpd[359]: connect from mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.248]
    postfix-mailcow-1 | Oct 1 14:52:24 ae0ccdcc0a15 postfix/sogo/smtpd[359]: EA7FA4D65B: client=mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.248], sasl_method=PLAIN, sasl_username=hansel@brillantinno.shop
    postfix-mailcow-1 | Oct 1 14:52:25 ae0ccdcc0a15 postfix/cleanup[362]: EA7FA4D65B: replace: header Received: from f6e681d9b29d (mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network [172.22.1.248])??(Authenticated sender: hansel@brillantinno.shop)??by mail.brillantinno.shop (Postcow) w from mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.248]; from=hansel@brillantinno.shop to=test-j12tq7ebg@srv1.mail-tester.com proto=ESMTP helo=<f6e681d9b29d>: Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPA id EA7FA4D65B??for test-j12tq7ebg@srv1.mail-tester.com; Tue, 1 Oct 2024 14:52:24 +0000 (UTC)
    postfix-mailcow-1 | Oct 1 14:52:25 ae0ccdcc0a15 postfix/cleanup[362]: EA7FA4D65B: message-id=<44-66fc0c80-5-6a4fcc00@91728783>
    postfix-mailcow-1 | Oct 1 14:52:25 ae0ccdcc0a15 postfix/qmgr[342]: EA7FA4D65B: from=hansel@brillantinno.shop, size=1100, nrcpt=1 (queue active)
    postfix-mailcow-1 | Oct 1 14:52:25 ae0ccdcc0a15 postfix/sogo/smtpd[359]: disconnect from mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.248] ehlo=1 auth=1 mail=1 rcpt=1 data=1 quit=1 commands=6
    postfix-mailcow-1 | Oct 1 14:52:55 ae0ccdcc0a15 postfix/smtp[363]: connect to reception.mail-tester.com[94.23.206.89]:25: Connection timed out
    postfix-mailcow-1 | Oct 1 14:52:55 ae0ccdcc0a15 postfix/smtp[363]: EA7FA4D65B: to=test-j12tq7ebg@srv1.mail-tester.com, relay=none, delay=31, delays=0.71/0.09/30/0, dsn=4.4.1, status=deferred (connect to reception.mail-tester.com[94.23.206.89]:25: Connection timed out)
    postfix-mailcow-1 | Oct 1 14:53:03 ae0ccdcc0a15 postfix/smtps/smtpd[368]: connect from cloud-scanner-d220c2c2.internet-research-project.net[50.116.52.105]
    postfix-mailcow-1 | Oct 1 14:53:05 ae0ccdcc0a15 postfix/smtps/smtpd[368]: SSL_accept error from cloud-scanner-d220c2c2.internet-research-project.net[50.116.52.105]: lost connection
    postfix-mailcow-1 | Oct 1 14:53:05 ae0ccdcc0a15 postfix/smtps/smtpd[368]: lost connection after CONNECT from cloud-scanner-d220c2c2.internet-research-project.net[50.116.52.105]
    postfix-mailcow-1 | Oct 1 14:53:05 ae0ccdcc0a15 postfix/smtps/smtpd[368]: disconnect from cloud-scanner-d220c2c2.internet-research-project.net[50.116.52.105] commands=0/0
    postfix-mailcow-1 | Oct 1 14:54:55 ae0ccdcc0a15 postfix/sogo/smtpd[376]: connect from mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.248]
    postfix-mailcow-1 | Oct 1 14:54:55 ae0ccdcc0a15 postfix/sogo/smtpd[376]: warning: Unable to look up MX host t1dxpo3fXK5myxrAZs4nWxtvBVhthitLB2y for Recipient address t1dxpo3fXK5myxrAZs4nWxtvBVhthitLB2y: Name or service not known
    postfix-mailcow-1 | Oct 1 14:54:55 ae0ccdcc0a15 postfix/sogo/smtpd[376]: E8B714D67C: client=mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.248], sasl_method=PLAIN, sasl_username=hansel@brillantinno.shop
    postfix-mailcow-1 | Oct 1 14:54:56 ae0ccdcc0a15 postfix/cleanup[379]: E8B714D67C: replace: header Received: from f6e681d9b29d (mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network [172.22.1.248])??(Authenticated sender: hansel@brillantinno.shop)??by mail.brillantinno.shop (Postcow) w from mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.248]; from=hansel@brillantinno.shop to=t1dxpo3fXK5myxrAZs4nWxtvBVhthitLB2y@mail.brillantinno.shop proto=ESMTP helo=<f6e681d9b29d>: Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPA id E8B714D67C??for <t1dxpo3fXK5myxrAZs4nWxtvBVhthitLB2y>; Tue, 1 Oct 2024 14:54:55 +0000 (UTC)
    postfix-mailcow-1 | Oct 1 14:54:56 ae0ccdcc0a15 postfix/cleanup[379]: E8B714D67C: message-id=<44-66fc0d00-9-6a4fcc00@91728849>
    postfix-mailcow-1 | Oct 1 14:54:56 ae0ccdcc0a15 postfix/qmgr[342]: E8B714D67C: from=hansel@brillantinno.shop, size=1104, nrcpt=1 (queue active)
    postfix-mailcow-1 | Oct 1 14:54:56 ae0ccdcc0a15 postfix/sogo/smtpd[376]: disconnect from mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.248] ehlo=1 auth=1 mail=1 rcpt=1 data=1 quit=1 commands=6
    postfix-mailcow-1 | Oct 1 14:55:26 ae0ccdcc0a15 postfix/smtp[380]: connect to mail.brillantinno.shop[13.50.121.248]:25: Connection timed out
    postfix-mailcow-1 | Oct 1 14:55:26 ae0ccdcc0a15 postfix/smtp[380]: E8B714D67C: to=t1dxpo3fXK5myxrAZs4nWxtvBVhthitLB2y@mail.brillantinno.shop, orig_to=<t1dxpo3fXK5myxrAZs4nWxtvBVhthitLB2y>, relay=none, delay=31, delays=0.31/0.11/30/0, dsn=4.4.1, status=deferred (connect to mail.brillantinno.shop[13.50.121.248]:25: Connection timed out)
    postfix-mailcow-1 | Oct 1 14:56:06 ae0ccdcc0a15 postfix/sogo/smtpd[376]: connect from mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.248]
    postfix-mailcow-1 | Oct 1 14:56:07 ae0ccdcc0a15 postfix/sogo/smtpd[376]: 247804D66D: client=mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.248], sasl_method=PLAIN, sasl_username=hansel@brillantinno.shop
    postfix-mailcow-1 | Oct 1 14:56:07 ae0ccdcc0a15 postfix/cleanup[379]: 247804D66D: replace: header Received: from f6e681d9b29d (mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network [172.22.1.248])??(Authenticated sender: hansel@brillantinno.shop)??by mail.brillantinno.shop (Postcow) w from mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.248]; from=hansel@brillantinno.shop to=youneszarhouni714@gmail.com proto=ESMTP helo=<f6e681d9b29d>: Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPA id 247804D66D??for youneszarhouni714@gmail.com; Tue, 1 Oct 2024 14:56:06 +0000 (UTC)
    postfix-mailcow-1 | Oct 1 14:56:07 ae0ccdcc0a15 postfix/cleanup[379]: 247804D66D: message-id=<44-66fc0d80-d-6a4fcc00@91728915>
    postfix-mailcow-1 | Oct 1 14:56:07 ae0ccdcc0a15 postfix/qmgr[342]: 247804D66D: from=hansel@brillantinno.shop, size=1135, nrcpt=1 (queue active)
    postfix-mailcow-1 | Oct 1 14:56:07 ae0ccdcc0a15 postfix/sogo/smtpd[376]: disconnect from mailcowdockerized-sogo-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.248] ehlo=1 auth=1 mail=1 rcpt=1 data=1 quit=1 commands=6
    postfix-mailcow-1 | Oct 1 14:56:08 ae0ccdcc0a15 postfix/smtp[380]: connect to gmail-smtp-in.l.google.com[2a00:1450:4010:c05::1b]:25: Network is unreachable
    postfix-mailcow-1 | Oct 1 14:56:38 ae0ccdcc0a15 postfix/smtp[380]: connect to gmail-smtp-in.l.google.com[64.233.162.26]:25: Connection timed out
    postfix-mailcow-1 | Oct 1 14:57:08 ae0ccdcc0a15 postfix/smtp[380]: connect to alt1.gmail-smtp-in.l.google.com[142.250.157.27]:25: Connection timed out
    postfix-mailcow-1 | Oct 1 14:57:09 ae0ccdcc0a15 postfix/smtp[380]: connect to alt1.gmail-smtp-in.l.google.com[2404:6800:4008:c13::1a]:25: Network is unreachable
    postfix-mailcow-1 | Oct 1 14:57:10 ae0ccdcc0a15 postfix/smtp[380]: connect to alt2.gmail-smtp-in.l.google.com[2607:f8b0:400e:c00::1a]:25: Network is unreachable
    postfix-mailcow-1 | Oct 1 14:57:10 ae0ccdcc0a15 postfix/smtp[380]: 247804D66D: to=youneszarhouni714@gmail.com, relay=none, delay=63, delays=0.3/0.01/63/0, dsn=4.4.1, status=deferred (connect to alt2.gmail-smtp-in.l.google.com[2607:f8b0:400e:c00::1a]:25: Network is unreachable)
    admin@ip-172-31-23-160:/opt/mailcow-dockerized$

      That is because Amazon EC2 blocks port 25 outgoing. You have to use Amazon SES.

      but I enabled smtp
      in my ec2 console

      esackbauer “In order to maintain the quality of Amazon EC2 addresses for sending email, we enforce default limits on the amount of email that can be sent from EC2 accounts. If you wish to send larger amounts of email from EC2, you can apply to have these limits removed from your account by filling out this form.” it seem they have just limitation not block

        You probably have hit the limits, maybe unintentionally, or someone who had your IP address before.
        The solution is in the link, use Amazon SES or ask them to remove the limit.

          No one is typing