-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
nixos/bind: Fix cacheNetworks option #335832
base: master
Are you sure you want to change the base?
Conversation
|
I agree with you that Also, I catched that the
Just in case you haven’t figured it out yet: with your branch checked out, from the nixpkgs root, run: On the current commit 8f16ef25cb2ee37cb1018e6cddaab82d93868858 I ran following tests, which were all successful:
|
I'll implement your recommendations soon. It took me quite some time just to rebase the PR and I ran out of time for this week. Thank you for your great review though. |
Ok nevermind, I could implement the changes just now.
The PR is now ready for review again. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with changing the doc & adding that short release note
Rebased again. @peti is there something blocking this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍, looks good to me.
I just rebased this for the I-dont-know-how-many-th time.
|
services.bind.cacheNetworks should only apply to recursive queryies, as per the option documentation: > Note that this is for recursive queries – all networks are allowed to > query zones configured with the zones option by default [...]. This would correspond to the `allow-query-cache` option in named.conf, as per the BIND docs[1]: > Specifies which hosts (an IP address list) can access this server’s > cache and thus effectively controls recursion. And not `allow-query`, which restricts all requests (including requests where the server has authority) [2]: > Specifies which hosts (an IP address list) are allowed to send queries > to this resolver. > [...] > Note: > `allow-query-cache` is used to specify access to the cache. [1]: https://bind9.readthedocs.io/en/v9.20.0/reference.html#namedconf-statement-allow-query-cache [2]: https://bind9.readthedocs.io/en/v9.20.0/reference.html#namedconf-statement-allow-query
Description of changes
services.bind.cacheNetworks should only apply to recursive queryies, as per the option documentation:
This would correspond to the
allow-query-cache
option in named.conf, as per the BIND docs1:And not
allow-query
, which restricts all requests (including requests where the server has authority) 2:Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.