[GH-ISSUE #118] Port Binding Errors #45

New issue

Closed

opened 2026-03-13 15:31:10 +03:00 by kerem · 3 comments

kerem commented

2026-03-13 15:31:10 +03:00

Owner

Originally created by @gespo89 on GitHub (Sep 30, 2018).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/118

Does this currently give any sort of visible error or warning if it can't bind the DNS port? I'll admit straight out that this largely is pebkac/rtfm error on my part, but I spent longer than I'd care to admit today troubleshooting today because systemd-resolved was hogging the port on Ubuntu server, putting this in a state where everything looked green everywhere I checked, no more config errors, register and update work fine, but nothing will resolve for obvious(in retrospect) reasons. It would be nice to have something a bit more in your face, like when you have config errors and it straight up spits out an error and refuses to start.

Originally created by @gespo89 on GitHub (Sep 30, 2018). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/118 Does this currently give any sort of visible error or warning if it can't bind the DNS port? I'll admit straight out that this largely is pebkac/rtfm error on my part, but I spent longer than I'd care to admit today troubleshooting today because systemd-resolved was hogging the port on Ubuntu server, putting this in a state where everything looked green everywhere I checked, no more config errors, register and update work fine, but nothing will resolve for obvious(in retrospect) reasons. It would be nice to have something a bit more in your face, like when you have config errors and it straight up spits out an error and refuses to start.

kerem closed this issue

2026-03-13 15:31:15 +03:00

kerem commented

2026-03-13 15:31:21 +03:00

Author

Owner

@coling commented on GitHub (Oct 22, 2018):

Seconded. I had the same issue. As systemd-resolved listens on 127.0.0.53:53 this blocks the all interfaces :53 default bind. Specifying 127.0.0.1:53 (for testing) or a real IP + port works fine. Some log information on this bind failure would be much appreciated (especially as systemd-resolved gets more widely deployed by default).

@coling commented on GitHub (Oct 22, 2018): Seconded. I had the same issue. As systemd-resolved listens on 127.0.0.53:53 this blocks the all interfaces :53 default bind. Specifying 127.0.0.1:53 (for testing) or a real IP + port works fine. Some log information on this bind failure would be much appreciated (especially as systemd-resolved gets more widely deployed by default).

kerem commented

2026-03-13 15:31:26 +03:00

Author

Owner

@joohoi commented on GitHub (Oct 30, 2018):

This should now be fixed!

@joohoi commented on GitHub (Oct 30, 2018): This should now be fixed!

kerem commented

2026-03-13 15:31:31 +03:00

Author

Owner

@jvanasco commented on GitHub (Oct 31, 2018):