On Mon, 2022-12-19 at 14:29 +0100, Thib D via Pdns-users wrote:
> Hi,
>
> Apologies for the misunderstanding,
>
> I was mentioning this warning from the pdns docs, but I'm not sure this
> also applies to bind-backend + sqlite setups:
> > It is not possible to replace the sqlite3 database file wh
Hi,
Apologies for the misunderstanding,
I was mentioning this warning from the pdns docs, but I'm not sure this
also applies to bind-backend + sqlite setups:
> It is not possible to replace the sqlite3 database file while PowerDNS is
> running. Specifically, using rsync to distribute sqlite3 dat
Hello,
You did not explain what you seeing and what you expect.
The warning concerns performance. But your questions suggests you are
seeing wrong data. Please be explicit.
-Otto
On Mon, Dec 19, 2022 at 11:02:34AM +0100, Thib D via Pdns-users wrote:
> Hi Chris,
>
> I missed this war
Hi Chris,
I missed this warning note on the sqlite3 backend page (
https://doc.powerdns.com/authoritative/backends/generic-sqlite3.html)
I'm scared this looks like the exact same behaviour we are seeing with a
bind+sqlite setup
After adding/modifying cryptokeys or metadata in the database, we are
Hello Thibauld,
* Thib D via Pdns-users [221216 14:19]:
> On bind / sqlite systems there is currently no way to reload metadata and
> cryptokeys provided through a read only sqlite3 database, correct ?
>
> pdns_control commands like bind-reload-now / bind-add-zone / reload do not
> seem to fetch
