[GH-ISSUE #135] Multiple IPs #52

New issue

Open

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

kerem commented

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

Owner

Originally created by @patrick7 on GitHub (Jan 24, 2019).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/135

Is it possible to listen on multiple specific IPs (IPv4 and IPv6)?
I have another DNS daemon running on another IP, so I'd like to bind acme-dns to a specific v4/v6 address.

Originally created by @patrick7 on GitHub (Jan 24, 2019). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/135 Is it possible to listen on multiple specific IPs (IPv4 and IPv6)? I have another DNS daemon running on another IP, so I'd like to bind acme-dns to a specific v4/v6 address.

kerem added the

feature request

label

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

kerem commented

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

Author

Owner

@joohoi commented on GitHub (Jan 25, 2019):

Hi! Unfortunately there isn't a way to handle this currently. Adding a label to track this later on.

@joohoi commented on GitHub (Jan 25, 2019): Hi! Unfortunately there isn't a way to handle this currently. Adding a label to track this later on.

kerem commented

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

Author

Owner

@lenovouser commented on GitHub (Mar 22, 2019):

You can temporarily solve this with Docker in theory

@lenovouser commented on GitHub (Mar 22, 2019): You can temporarily solve this with Docker in theory

kerem commented

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

Author

Owner

@voltagex commented on GitHub (Sep 11, 2021):

@joohoi ping - just hit this one too.

@voltagex commented on GitHub (Sep 11, 2021): @joohoi ping - just hit this one too.

kerem commented

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

Author

Owner

@candlerb commented on GitHub (Feb 21, 2022):

Specific use case: you have a dual-stack host with systemd-resolved listening on 127.0.0.53:53, so you need to bind explicitly to the public IPv4 address and the public IPv6 address.

(Or else you need to work out how to disable systemd-resolved cleanly and put resolution back to how it used to work in the old days)

EDIT: although according to #63, if a system only listens on IPv6, LetsEncrypt is still guaranteed to work.

@candlerb commented on GitHub (Feb 21, 2022): Specific use case: you have a dual-stack host with systemd-resolved listening on 127.0.0.53:53, so you need to bind explicitly to the public IPv4 address and the public IPv6 address. (Or else you need to work out how to disable systemd-resolved cleanly and put resolution back to how it used to work in the old days) EDIT: although according to #63, if a system only listens on IPv6, LetsEncrypt is still [guaranteed to work](https://letsencrypt.org/docs/ipv6-support/).