feat: Support listening on multiple individual IPs #393
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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