• Community SupportUnbound
  • USEnglish

  • Unhealthy mailcowdockerized-unbound-mailcow-1: Failed to con. “www.internic.net”

I’m trying to get mailcow work with default settings on a fresh alpine (aarch64) with no firewall (iptables and nftables only), but there is some network issue.

My issue is similar to the following mailcow community Icon problem

mailcow community Icon mailcow communityDiscussion
I cant install mailcow and it shows and dns error
Author avatar image LukasHuth
The unhealthy docker is mailcowdockerized-unbound-mailcow-1 I already tried to update it and the docker log for it shows: curl: (7) Failed to connect to “www.internic.net” port 443 after 3216 ms: Couldn’t connect to server this is my os: PRETTY_NAME=“Ubuntu 22.04.3 LTS” NAME=“Ubuntu”
mailcow community
8 4
: curl: (7) Failed to connect to “www.internic.net” port 443 after 3216 ms: Couldn’t connect to server.I was not able to bypass this by disabling ipv6.

curl -vo /tmp/root.hints https://www.internic.net/domain/named.cache
works from host but not from unbound container

Ports seem to be closed for an outer computer in LAN: bpa.st Icon View paste YVYA

bpa.st Icon bpa.st
View paste YVYA
bpa.st

My ip a from unbound container: bpa.st Icon View paste AYAQ

bpa.st Icon bpa.st
View paste AYAQ
bpa.st

Here is ps aux | grep docker-proxy: bpa.st Icon View paste D55A

bpa.st Icon bpa.st
View paste D55A
bpa.st

Seems like the problem is related to docker-proxy setup

    Here is my healthcheck.log

    8844ce6e22f6:/# cat /var/log/healthcheck.log
2024-06-28 11:22:37: Please check your internet connection or firewall rules to fix this error, because a simple ping test should always go through from the unbound container!
8844ce6e22f6:/# ping 1.1.1.1

    I know that this problem is setup specific but I’m installing mailcow on a fresh new Alpine without firewall. I’m ready to cooperate and trace packages. Please help.

    Here is my traceroute from unbound container:

    8844ce6e22f6:/# cat /var/log/healthcheck.log
2024-06-28 11:22:37: Please check your internet connection or firewall rules to fix this error, because a simple ping test should always go through from the unbound container!
8844ce6e22f6:/# ping 1.1.1.1

    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!

    Sorry, wrong traceback copypaste. Right one:

    8844ce6e22f6:/# traceroute google.com
traceroute to google.com (142.251.1.102), 30 hops max, 46 byte packets
 1  172.22.1.1 (172.22.1.1)  0.006 ms  0.013 ms  0.006 ms
 2  *  *  *
    No one is typing