problems serving a secondary zone from SQLite

[JINMEI Tatuya / 神明達哉]

At Fri, 15 Feb 2013 17:35:39 +0100,
Carsten Strotmann <carsten at strotmann.de> wrote:

> just after sending this mail I found a workaround, but I'm not sure if
> this is how it should be.
> 
> If I enable caching on the zone, it works:
> 
> > config set data_sources/classes/IN[1]/cache-zones[1]
> > "dnsworkshop.org" config commit
> 
> If caching also required for SQLite zones?

No, but if you enable "caching", all zones stored in the underlying
SQLite3 data source must be listed in "cache-zones".  That is, you
should either

1. disable cache (sqlite3 only)
2. enable cache, and list all zones in cache-zones

In your original configuration, you enabled cache but not listed
"dnsworkshop.org" in cache-zones:

data_sources/classes/IN[1]/type "sqlite3"       string
data_sources/classes/IN[1]/params       {"database_file":
"/var/bind10/zones.db"}       any
data_sources/classes/IN[1]/cache-enable true    boolean
data_sources/classes/IN[1]/cache-zones[0]       "example.org"   string

In your revised config you added it to cache-zones (#2 above), so it
works.  You can also disable cache (#1 above).

I admit the config/documentation is not friendly enough in this area.

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.