Add SourceFilterApp #1423
Open
Add SourceFilterApp #1423
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
|
Thanks for the PR. Will check this and let you know soon. |
Signed-off-by: Denis Kudelin <[email protected]>
…gth clamp Signed-off-by: Denis Kudelin <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What’s new
• Added per-rule splitNetworks field.
• splitNetworks now accepts either a plain CIDR string or an object { "network": "", "samePrefix": }.
• The optional samePrefix lets you restrict internal replies to records that share the first N bits with the client (e.g. serve 10.34.* only to 10.34.0.0/16 clients within the broader 10.0.0.0/8).
• Prefix length is clamped to the address size; out-of-range values are ignored.
• Back-compatible: legacy string syntax ("10.0.0.0/8") still works unchanged.
• Clients inside the listed networks receive only internal A/AAAA addresses; outsiders get external ones.
• Fully interoperates with existing includeNetworks / excludeNetworks.
Why
Many deployments must expose both private and public IPs for the same FQDN
without duplicating zones.
splitNetworks enables true split-horizon responses in a single,
self-contained config, simplifying maintenance and eliminating the need for
separate translation plugins.