-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Docker v26.0.0 breaks DNS #5800
Comments
Any update on this please? People on Docker v26 will have no RBL functionality on their server until we find a fix. Thank you |
@dogsbody where exactly are you seeing these log messages? |
With either of these commands
Here's another line from another Mailcow server from a few minutes ago
|
Oh - I only checked the container logs. Thanks! |
hi, I also see errors
|
Hey
|
It seems others are having this issue as well :-( I believe that those of us on Docker v26.0 no longer have DNS RBL protection for our mailcow instances. |
What does Postfix's Logs say? If there are sections from Spamhaus regarding: listed on 127.0.0.X it is working as expected. |
actually I see these entries in the postfix log...
|
Yeah that is the expected behaviour. |
I'm following this issue with interest, but I'm not sure what the status is now. There are error messages in the journal, but the DNS blocklists still work? I'm a bit confused... I have seen that there is now a v26.0.1 release that has changed something in the DNS resolution again:
Does that change anything? EDIT: Sorry, I'm just now realizing that the changes only affect |
Confirmed. I updated to v26.0.1 last night and got all the same errors overnight :-( |
Digging into this a little, I noticed that the error happens on the initial connect and not during the dnsbl lookup. It seems that when it cannot complete a reverse lookup (Doesn't happen all the time) it produces the error from docker we are seeing about a timeout. If you have verbose logging on unbound eventually it produces an error like the following: So, this seems to be an upstream DNS failure that is now being reported differently by docker v26. EDIT: Docker v26: |
I can confirm the tests of @kilo666mj with Docker v25. What I still wonder: Are the error messages now works-as-designed or is there really a bug here? |
Interestingly, since upgrading from Docker v26.0.0 to v26.0.1 I have also started getting the additional error... |
We have come to the conclusion that nothing is actually broken. Docker is now just being more verbose about DNS entries that don't resolve (NXDOMAIN). We have done tests from both inside and out of the docker containers and DNS seems to be looking up fine. It's only DNS lookups that result in a NXDOMAIN that produce the log. |
Contribution guidelines
I've found a bug and checked that ...
Description
Source: https://docs.docker.com/engine/release-notes/26.0/#bug-fixes-and-enhancements
Steps to reproduce:
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Ubuntu 22.04 LTS
Server/VM specifications:
2 cores, 4GB RAM
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
KVM I think, it's a VPS server
Docker version:
v26.0.0
docker-compose version or docker compose version:
v2.25.0
mailcow version:
2024-02
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: