So I recently installed mailcow, but I’ve gotten stuck at the unbound container giving me healthcheck issues. I chased a bunch of random rabbit trails, to no avail. I randomly checked /etc/resolv.conf, as I as checking it on my host server&vm for any ideas, and I saw that the FallbackDNS line didn’t have an equal sign in it. This gives me the slight idea that whatever set this up is causing the Unhealthy issue.

nameserver 127.0.0.11
options ndots:0
DNSStubListener=no
DNS=1.1.1.1
FallbackDNS8.8.8.8

However, I don’t know what process is changing that file after reboot, as it removes the = that I put in. It doesn’t appear to be a symlink inside the container, but I don’t see anything obvious that might be changing it.

    thecodingchicken DNSStubListener=no
    DNS=1.1.1.1
    FallbackDNS8.8.8.8

    These seem to be overrides from yourself? I don’t have these lines in my resolv.conf inside my unbound container

      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!

      It seems that was it, I had a typo in the host system. Unfortunately, it didn’t solve the unhealthy issues.
      It seems that the unbound service doesn’t want to work still. As shown in the image, I can resolve if I don’t use unbound, which defeats the purpose of the container if I understand it correctly.

      Are there any other configs that I should look into that may fix it?

      Which OS are you running? Do you have selinux enabled? Please share your specs

      Sorry for the delay, I was busy this evening.
      I’m running Ubuntu server 24.04.1 LTS inside a vm, SELinux is disabled. The vm has two cores and 4 gigs of ram currently, which, according to the recent tutorial that I was following, should be good enough to get everything setup.
      Everything has internet access, and can resolve addresses until I attempt to run it through unbound.

      I’ll reply in the morning if anyone has any clues. I haven’t had time to look into it due to longer work days.

      Ok, disabled all firewalls, the physical os shouldn’t have affected it.
      The vm now has 8G of ram as well

      Changed some router setting, and I think it worked? Some step allowed it to work.
      First resolve takes some time, then everything after that is instant.
      Nginx was throwing some errors next, I don’t get these issues, as this is stock mailcow straight from the github.
      I didn’t see that config file in data/conf/nginx, so I was just confused about that

      Final update. Got to the “What is happening page”
      Followed the instructions, wiped volumes and restarted everything.
      Now unbound works and I have access to the admin page(finally, only took a couple days)

      Final update. Got to the “What is happening page”
      Followed the instructions, wiped volumes and restarted everything.
      Now unbound works and I have access to the admin page(finally, only took a couple days)

      No one is typing