ComputerSurge/bind9
3
0
Fork 0
Code Pull Requests 1 Activity

Remove the DLZ driver documentation

Browse Source 
Remove the last traces of static DLZ drivers from ARM.
This commit is contained in:
Ondřej Surý
2021-09-21 10:56:05 +02:00
parent 0b983fe2e5
commit 5acac71f20
1 changed files with 3 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
doc/arm/dlz.rst
View File

@@ -15,24 +15,10 @@ Dynamically Loadable Zones (DLZ)
Dynamically Loadable Zones (DLZ) are an extension to BIND 9 that allows
zone data to be retrieved directly from an external database. There is
no required format or schema. DLZ drivers exist for several different
database backends, including PostgreSQL, MySQL, and LDAP, and can be
no required format or schema. DLZ modules exist for several different
database backends, including MySQL and LDAP, and can be
written for any other.
Historically, DLZ drivers had to be statically linked with the ``named``
binary and were turned on via a configure option at compile time (for
example, ``configure --with-dlz-ldap``). The drivers
provided in the BIND 9 tarball in ``contrib/dlz/drivers`` are still
linked this way.
In BIND 9.8 and higher, it is possible to link some DLZ modules
dynamically at runtime, via the DLZ "dlopen" driver, which acts as a
generic wrapper around a shared object implementing the DLZ API. The
"dlopen" driver is linked into ``named`` by default, so configure
options are no longer necessary when using these dynamically linkable
drivers; they are still needed for the older drivers in
``contrib/dlz/drivers``.
The DLZ module provides data to ``named`` in text
format, which is then converted to DNS wire format by ``named``. This
conversion, and the lack of any internal caching, places significant
@@ -87,7 +73,7 @@ backend storage of redirection rules:
};
Sample DLZ Driver
Sample DLZ Module
~~~~~~~~~~~~~~~~~
For guidance in the implementation of DLZ modules, the directory