-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New install, acme cannot resolv DNS #5998
Comments
Duplicate #5973? |
I thought about that, I don't get the
|
I just noticed that I can do a lookup on a different domain, with AAAA records, but the one without gives me the SERVFAIL. |
I'm having this issue too and I've just installed mailcow. The logs are full of dns errors and it let me create a new mailbox but if I try to access it using SOGo I get "No mailbox selected" and trying to do some actions just fails with a general error. Using a mail client like thunderbird fails too |
THIS IS A AUTOMATED MESSAGE! It seems your issue is not a bug. You can get support either by:
This issue will be closed. If you think your reported issue is not a support case feel free to comment above and if so the issue will reopened. |
I think this is a bug. It worked a couple weeks ago and now it does not work anymore.
Clearly a bug.
|
Server, that has been running mailcow, the lookup works without an issue.
Brand new VM (Ubuntu 24.04) fully updated with the most current docker etc. nslookup within acme does not work at all.
|
@DerLinkman @DTrombett |
@denis-ev Thanks a lot for your reply! Although this works, it seems that mailcow discourages doing this ("Important: Only DNSSEC validating DNS services will work.") and it indeed brakes something as I can send and receive emails from SOGo but cannot log in from another client like Thunderbird |
And your DNS Blocklists will stop working, those two reasons are why we installed unbound in the first place, see https://docs.mailcow.email/manual-guides/u_e-why_unbound |
@DTrombett yeah I changed only the DNS for acme and not in Unbound basically: docker-compose.override.yml services:
acme-mailcow:
dns:
- 1.1.1.1
- 1.0.0.1 |
Interesting, I'll try that, thanks! |
Might work, but that is only a workaround. You have to fix your dns resolution inside a docker network... We won't support such crappy "fixes", be aware of that! And before this comes up: "DNS Resolution on my host works" might be but then something inside your network is broken as a normal mailcow setup has no problem with that! To address this it might be hard to debug, as you have to on the network side of your server. |
@DerLinkman nslookup in the unbound container does work, just not in the acme container, which is really confusing. edit: even spun up another server with a freshly installed ubuntu 24.04, same issue |
Sadly, this didn't work for me. Running |
@DerLinkman FYI Just did the update and it's working again |
Contribution guidelines
I've found a bug and checked that ...
Description
Logs:
Steps to reproduce:
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Ubuntu 24.04 LTS
Server/VM specifications:
16GB, 8 Cores
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
VMWare
Docker version:
27.1.1
docker-compose version or docker compose version:
v2.29.1
mailcow version:
2024-07
Reverse proxy:
none
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check:
The text was updated successfully, but these errors were encountered: