[GH-ISSUE #129] Documentation and example config mismatch #50

New issue

Closed

opened 2026-03-13 15:33:03 +03:00 by kerem · 2 comments

kerem commented

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

Owner

Originally created by @jamestutton on GitHub (Dec 10, 2018).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/129

Hi just testing this and firstly great project.

One issue that caused me some issues though is the example docker config is mismatched with the example config.cfg Issue being

docker -p53:53 binds tcp port 53 for the container whilethe example config.cfg is listening to udp port 53.

So it either needs -p 53:53/udp preferred or the config.cfg updated to protocol = "tcp"

docker run --rm --name acmedns                 \
 -p 53:53/udp                                      \
 -p 80:80                                      \
 -v /path/to/your/config:/etc/acme-dns:ro      \
 -v /path/to/your/data:/var/lib/acme-dns       \
 -d joohoi/acme-dns

As it stands I suspect a number of people new to docker will fall at this hurdle and this great project will not get the support or consideration it deserves.

Originally created by @jamestutton on GitHub (Dec 10, 2018). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/129 Hi just testing this and firstly great project. One issue that caused me some issues though is the example docker config is mismatched with the example config.cfg Issue being docker -p53:53 binds tcp port 53 for the container whilethe example config.cfg is listening to udp port 53. So it either needs -p 53:53/udp **preferred** or the config.cfg updated to protocol = "tcp" ``` docker run --rm --name acmedns \ -p 53:53/udp \ -p 80:80 \ -v /path/to/your/config:/etc/acme-dns:ro \ -v /path/to/your/data:/var/lib/acme-dns \ -d joohoi/acme-dns ``` As it stands I suspect a number of people new to docker will fall at this hurdle and this great project will not get the support or consideration it deserves.

kerem closed this issue

2026-03-13 15:33:09 +03:00

kerem commented

2026-03-13 15:33:14 +03:00

Author

Owner

@jcormier commented on GitHub (Dec 12, 2018):

Yes this just tripped me up for a few days. Had to update the docker-compose to use port 53/udp

github.com/joohoi/acme-dns@20411b650f/docker-compose.yml (L10)

@jcormier commented on GitHub (Dec 12, 2018): Yes this just tripped me up for a few days. Had to update the docker-compose to use port 53/udp https://github.com/joohoi/acme-dns/blob/20411b650f7a60b7d6036a56fb1d0d67c46e291f/docker-compose.yml#L10

kerem commented

2026-03-13 15:33:20 +03:00

Author

Owner

@joohoi commented on GitHub (Dec 13, 2018):

Thanks for your kind words, and nice catch! This should now be fixed in #130 . I decided to add a requested (and sane) feature to bind DNS listener to both - UDP and TCP ports at the same time. This combination should make acme-dns more convinient to use.

@joohoi commented on GitHub (Dec 13, 2018): Thanks for your kind words, and nice catch! This should now be fixed in #130 . I decided to add a requested (and sane) feature to bind DNS listener to both - UDP and TCP ports at the same time. This combination should make `acme-dns` more convinient to use.

kerem referenced this issue

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

[PR #50] [MERGED] Properly parse r.RemoteAddr #262