configuration flags, which you should configure (when available) using
the PowerDNS native configuration.
-**note**: Because this backend retrieves its configuration from a text file 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.
+.. note::
+ Because this backend retrieves its configuration from a text file 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.
Configuration Parameters
------------------------
Native zones in the BIND backend are supported since version 4.1.0 of
the PowerDNS Authoritative Server.
-**note**: Any zone with no ``type`` set (an error in BIND) is assumed to
-be native.
+.. note::
+ Any zone with no ``type`` set (an error in BIND) is assumed to be native.
Released June 29th 2016
-**note**: rc1 was tagged in git but never officially released. Kees
-Monshouwer discovered an issue in the gmysql backend that would
-terminate the daemon on a connection error, this fixed in rc2.
+.. note::
+ rc1 was tagged in git but never officially released. Kees
+ Monshouwer discovered an issue in the gmysql backend that would
+ terminate the daemon on a connection error, this fixed in rc2.
This Release Candidate adds IXFR consumption and fixes some issues with
prepared statements:
If this is disabled (the default), ALIAS records will not expanded and
the server will will return NODATA for A/AAAA queries for such names.
-**note**: :ref:`setting-resolver` must also be set for ALIAS
-expansion to work!
+.. note::
+ :ref:`setting-resolver` must also be set for ALIAS expansion to work!
-**note**: In PowerDNS Authoritative Server 4.0.x, this setting did not
-exist and ALIAS was always expanded.
+.. note::
+ In PowerDNS Authoritative Server 4.0.x, this setting did not exist and
+ ALIAS was always expanded.
.. _setting-forward-dnsupdate: