Unbound health check and IPv6

Skittluier

Hi all,

My server doesn’t ping to IPv4 addresses anymore and only likes IPv6 from now on.
Now the unbound-mailcow healthcheck script only pings to IPv4 addresses at the moment.

Is there a way for me to adjust something within a config file to make sure these health checks are being done through IPv6?

Thanks in advance!

DocFraggle

You can disable the health check in mailcow.conf

SKIP_UNBOUND_HEALTHCHECK

Skittluier

DocFraggle
Thanks for the swift answer!
I could do that, however it’s not recommended at all to do that. I thought maybe there would be a more clean solution. 🤔

DocFraggle

Well, you could manually add “-6” to the ping command:

mailcow/mailcow-dockerizedblob/bd9f4ba0a57a159939760ecd319f2d44abf6b27a/data/Dockerfiles/unbound/healthcheck.sh#L20

But you would have to do that again with every update as the file will be overwritten…

Edit: and you have to replace the ipv4 addresses with IPv6 addresses here:

mailcow/mailcow-dockerizedblob/bd9f4ba0a57a159939760ecd319f2d44abf6b27a/data/Dockerfiles/unbound/healthcheck.sh#L13

Edit 2: btw, running a mail server IPv6 only without the possibility to reach v4 addresses isn’t a good idea at all, as there are many mail servers which run IPv4 only! You won’t be able to send mails there

Skittluier

DocFraggle

Oh dear, that sounds pretty bad. I’m going to investigate how to have an IPv4 address as well then.
Thank you!

Skittluier

For the people experiencing the same issue and being stuck with this issue as well - this is what helped me: https://superuser.com/a/237122

To be precise, the command is dhcpcd eno1 (eno1 is the name of my ethernet adapter)

Now I need to find a way to start this lease by default, because it seems it’s not happening by default at all…