From c7882d8c31a1d4549e6664d576ca84a62c9a3009 Mon Sep 17 00:00:00 2001 From: Gert van Dijk Date: Sun, 31 Mar 2019 19:25:22 +0200 Subject: [PATCH] docs: Add paragraph on benefits of the BIND backend --- docs/backends/bind.rst | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/backends/bind.rst b/docs/backends/bind.rst index 4a18f255f3..b8b8c73eb1 100644 --- a/docs/backends/bind.rst +++ b/docs/backends/bind.rst @@ -22,8 +22,13 @@ information about zones from it. It makes no attempt to honour other configuration flags, which you should configure (when available) using the PowerDNS native configuration. +Unique to this PowerDNS backend is that it serves from plain zone files, +which allows for hand-crafting zone files, only takes a tiny footprint +in terms of server resource usage while being +:ref:`performant efficiently `. + .. note:: - Because this backend retrieves its configuration from a text file and + Because this backend retrieves its configuration from plain files and not a database, the HTTP API is unable to process changes for this backend. This effectively makes the API read-only for zones hosted by the BIND backend. @@ -152,6 +157,8 @@ removed from memory. All zones with a changed timestamp are reloaded at the next incoming query for them. +.. _bind_performance: + Performance ----------- -- 2.47.2