-
-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conditional groups #1462
Comments
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Not stale |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Not stale, I think I might write up a PR for this... it would be my first time writing go though, so its gonna take a while to get something decent |
In both
upstreams
andblocking
we can define rules ("groups") for which source hits which resolver/blocklist, but this is not a thing forconditional
.I would like to, as an example, not allow my guest network to resolve my internal authoritative server, only upstreams and/or blocking.
An example wishful configuration (not a direct proposal):
In cases where you wouldn't want a client to reach any mappings it could be an empty list, e.g:
This should be optional, both for brievity in the config and for backwards compatibility.
The text was updated successfully, but these errors were encountered: