mirror of
https://github.com/acme-dns/acme-dns.git
synced 2026-04-27 04:45:48 +03:00
[PR #393] feat: Support listening on multiple individual IPs #399
Labels
No labels
Documentation
Documentation
bug
enhancement
feature request
feature request
help wanted
pull-request
question
security
security
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/acme-dns#399
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/acme-dns/acme-dns/pull/393
Author: @zajdee
Created: 11/24/2025
Status: 🔄 Open
Base:
master← Head:support-multiple-ips📝 Commits (4)
6b09259feat: Support listening on multiple individual IPs6043d5bProperly support udp4/udp6/tcp4/tcp6 too84aa069Remove a forgotten return line6282740Further simplify getProtocols📊 Changes
2 files changed (+58 additions, -26 deletions)
View changed files
📝
main.go(+57 -25)📝
main_test.go(+1 -1)📄 Description
Hello,
this change adds support of specifying multiple explicitly configured listening IP addresses. This was previously not possible - either the service was listening on
any(0.0.0.0/::) or on one address picked up by the operator (which may not be enough in dual-stacked environments).This is useful in environments where you have multiple DNS servers listening on 53 (udp or tcp) and you want to distinguish between them by IPs. One DNS server may be listening on
127.0.0.1:53, [::1]:53, and another one on public IPs, e.g.192.0.2.1:53,[2001:db8::1]:53.Likely resolves #135
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.