You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could you add support for "key" statement in address_match_element statements?
These are handy, for instance, in 'match-client' clauses in views to plumb views through filtering tools, for instance, OpenDNSSEC, without having to use extra IP addresses (or extra 127/8 addresses).
For example:
view "lab-unsigned" {
match-clients { key "lab-outgoing"; };
zone "lab.example.com" {
type master;
file "lab.example.com.zone";
allow-transfer { key "lab-outgoing"; };
also-notify {
127.0.0.1 port 5353 key "lab-outgoing";
};
};
};
The text was updated successfully, but these errors were encountered:
Could you add support for "key" statement in address_match_element statements?
These are handy, for instance, in 'match-client' clauses in views to plumb views through filtering tools, for instance, OpenDNSSEC, without having to use extra IP addresses (or extra 127/8 addresses).
For example:
The text was updated successfully, but these errors were encountered: