[GH-ISSUE #304] Will systemd-resolve get in the way? #160

New issue

Closed

opened 2026-03-13 16:01:14 +03:00 by kerem · 3 comments

kerem commented

2026-03-13 16:01:14 +03:00

Owner

Originally created by @thedarb on GitHub (May 8, 2022).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/304

My standard Ubuntu systems (20.04 - 22.04) all came configured with systemd-resolve parked on the DNS port (53):

$ sudo netstat -lpn | grep ":53 "
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      710/systemd-resolve 
udp        0      0 127.0.0.53:53           0.0.0.0:*                           710/systemd-resolve

I'm thinking if I want to run this as a Docker container, I might need to set it up with it's own IP on my lan for this. I suppose I could disable systemd-resolv, but I don't yet know the implications of trying that. Thoughts?

Originally created by @thedarb on GitHub (May 8, 2022). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/304 My standard Ubuntu systems (20.04 - 22.04) all came configured with systemd-resolve parked on the DNS port (53): ``` $ sudo netstat -lpn | grep ":53 " tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 710/systemd-resolve udp 0 0 127.0.0.53:53 0.0.0.0:* 710/systemd-resolve ``` I'm thinking if I want to run this as a Docker container, I might need to set it up with it's own IP on my lan for this. I suppose I could disable systemd-resolv, but I don't yet know the implications of trying that. Thoughts?

kerem closed this issue

2026-03-13 16:01:20 +03:00

kerem commented

2026-03-13 16:01:26 +03:00

Author

Owner

@thedarb commented on GitHub (May 9, 2022):

Nevermind. :)

@thedarb commented on GitHub (May 9, 2022): Nevermind. :)

kerem commented

2026-03-13 16:01:31 +03:00

Author

Owner

@Ajedi32 commented on GitHub (May 9, 2022):

In the interest of avoiding "nevermind, I fixed it" syndrome here:

Yes, it does interfere, and the solution is either to update the listen option in config.cfg to bind to a specific IP address (such as 127.0.0.1, or the public IP of your box), or set DNSStubListener=no in /etc/systemd/resolved.conf to stop systemd from listening on that port. (And manually update the resolv.conf symlink if you're running systemd <v246.)

@Ajedi32 commented on GitHub (May 9, 2022): In the interest of avoiding "nevermind, I fixed it" syndrome here: Yes, it does interfere, and the solution is either to update the `listen` option in `config.cfg` to bind to a specific IP address (such as 127.0.0.1, or the public IP of your box), or set `DNSStubListener=no` in `/etc/systemd/resolved.conf` to stop systemd from listening on that port. (And [manually update the `resolv.conf` symlink if you're running systemd <v246](https://github.com/systemd/systemd/issues/14700#issuecomment-1046279509).)

kerem commented

2026-03-13 16:01:36 +03:00

Author

Owner

@thedarb commented on GitHub (May 10, 2022):

Yep, binding it to 127.0.0.1 did it for me. Ubuntu 22.04. Thank you.

@thedarb commented on GitHub (May 10, 2022): Yep, binding it to 127.0.0.1 did it for me. Ubuntu 22.04. Thank you.