BIND 10 #1911: document how to configure in-memory data source with sqlite3 backend
BIND 10 Development
do-not-reply at isc.org
Tue May 15 04:54:43 UTC 2012
#1911: document how to configure in-memory data source with sqlite3 backend
-------------------------------------+-------------------------------------
Reporter: | Owner: muks
jinmei | Status: reviewing
Type: task | Milestone:
Priority: | Sprint-20120515
medium | Resolution:
Component: | Sensitive: 0
documentation | Sub-Project: DNS
Keywords: | Estimated Difficulty: 3
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: xfr |
for in-memory |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by muks):
Replying to [comment:6 jinmei]:
> Replying to [comment:5 muks]:
>
> > > The "incoming zone" in "In the case of an incoming zone" sounds
> > > awkward, that is, what's "incoming zone"? Do you mean "incoming
zone
> > > transfer" (but then "which is served..." doesn't make much sense)?
Or
> > > maybe it should be "secondary zone"? I think this sentence should
be
> > > clarified.
> >
> > This text has been updated now.
>
> Okay, it's now clearer. A few more small points:
>
> - I'd replace "data source file" with "data source" because "data
> source" is a more abstract notion that a concrete "file"
> - Similarly, I'd simply say "backend" instead of "backend file".
>
Done. :)
> > > I'd also clarify what the administrator should do (or doesn't have
to)
> > > if they want to serve a zone from in-memory for normal queries while
> > > updating it by incoming zone transfers.
> >
> > I don't follow this. Can you say what you want to see?
>
> Something like this: "The administrator doesn't have to do anything
> for b10-auth to serve the new version of zone except for the
> configuration such as the one described in <reference to
> in-memory-datasource-with-sqlite3-backend>".
Added. :)
--
Ticket URL: <http://bind10.isc.org/ticket/1911#comment:8>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list