BIND 10 #2046: Special case for loading zone files to In-Memory in ClientList config
BIND 10 Development
do-not-reply at isc.org
Thu Jul 5 13:29:13 UTC 2012
#2046: Special case for loading zone files to In-Memory in ClientList config
-------------------------------------+-------------------------------------
Reporter: | Owner: jelte
vorner | Status: reviewing
Type: task | Milestone:
Priority: | Sprint-20120717
medium | Resolution:
Component: data | Sensitive: 0
source | Sub-Project: DNS
Keywords: | Estimated Difficulty: 4
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by vorner):
* owner: vorner => jelte
Comment:
Hello
Replying to [comment:9 jelte]:
> part of the potential confusion/unexpected result may be that it's not
really what most people consider a cache :) I can see erroring instead of
loading to enforce its explicit setting, but given the second one, that is
a specific use-case, which may make sense, I'm just a bit afraid that
people think they have it loaded because it is silently ignored.
Well, we need to support that use case, because that one is very real for
us. And the `allow_cache` is set by the application, not by the user (so
user can't set it to false in auth and be surprised it doesn't work). The
MasterFiles type needs a warning in the documentation it does not work for
XFROut/XFRIn.
What we can do is adding a warning to logs in such case. We could also
special-case the MasterFiles type somehow in the XFROut, but it makes
little sense for XFRIn. But that'd go to a separate ticket.
Or, do you have any other idea?
--
Ticket URL: <http://bind10.isc.org/ticket/2046#comment:10>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list