[GH-ISSUE #224] Not working with docker swarm #107

New issue

Closed

opened 2026-03-13 15:47:44 +03:00 by kerem · 1 comment

kerem commented

2026-03-13 15:47:44 +03:00

Owner

Originally created by @tom-eagle92 on GitHub (Apr 8, 2020).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/224

Hi,
I'm trying to get this working with docker swarm and traefik on an Ubuntu server.
It's nearly working fine, but as soon as I start the stack with the acme-dns the dns on the host stops working. I can make queries with dig from my laptop to the server as in the example in the README, but when I try 'dig google.com' the response is empty, after stopping the stack it is working again.
In the config I need 'listen = "0.0.0.0:53"' with 'listen = "127.0.0.1:53"' nothing is working when the container is running. Neither from my laptop to the server nor any dig on the server.
What do I have to configure to get this working completely?
I already searched a lot with google but was not able to find a solution

Originally created by @tom-eagle92 on GitHub (Apr 8, 2020). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/224 Hi, I'm trying to get this working with docker swarm and traefik on an Ubuntu server. It's nearly working fine, but as soon as I start the stack with the acme-dns the dns on the host stops working. I can make queries with dig from my laptop to the server as in the example in the README, but when I try 'dig google.com' the response is empty, after stopping the stack it is working again. In the config I need 'listen = "0.0.0.0:53"' with 'listen = "127.0.0.1:53"' nothing is working when the container is running. Neither from my laptop to the server nor any dig on the server. What do I have to configure to get this working completely? I already searched a lot with google but was not able to find a solution

kerem closed this issue

2026-03-13 15:47:49 +03:00

kerem commented

2026-03-13 15:47:55 +03:00

Author

Owner

@tom-eagle92 commented on GitHub (Apr 8, 2020):

Ok, just found the solution:
https://medium.com/@niktrix/getting-rid-of-systemd-resolved-consuming-port-53-605f0234f32f

@tom-eagle92 commented on GitHub (Apr 8, 2020): Ok, just found the solution: https://medium.com/@niktrix/getting-rid-of-systemd-resolved-consuming-port-53-605f0234f32f