To compile a module for inclusion at runtime, which is great if you are a unix vendor, use ``--with-dynmodules='mod1 mod2 mod3'``.
These modules then end up as .so files in the compiled ``libdir``.
-By default, the :doc:`bind <../../backends/bind>`, :doc:`mysql <../../backends/generic-mysql>` and :doc:`random <../../backends/random>` are compiled into the binary. The :doc:`pipe <../../backends/pipe>` is, by default, compiled as a runtime loadable module.
+By default, the :doc:`bind <../../backends/bind>`, :doc:`mysql <../../backends/generic-mysql>` and :doc:`random <../../backends/random>` modules are compiled into the binary. The :doc:`pipe <../../backends/pipe>` is, by default, compiled as a runtime loadable module.
Getting the sources
-------------------
If this is enabled, ALIAS records are expanded (synthesised to their
A/AAAA).
-If this is disabled (the default), ALIAS records will not expanded and
+If this is disabled (the default), ALIAS records will not be expanded and
the server will will return NODATA for A/AAAA queries for such names.
.. note::
:ref:`metadata-also-notify` domain metadata to avoid this potential bottleneck.
.. note::
- If your slaves support Internet Protocol version, which your master does not,
+ If your slaves support an Internet Protocol version, which your master does not,
then set ``only-notify`` to include only supported protocol version.
Otherwise there will be error trying to resolve address.
- Integer
- 60
-On a master, this is the amounts of seconds between the master checking
+On a master, this is the amount of seconds between the master checking
the SOA serials in its database to determine to send out NOTIFYs to the
slaves. On slaves, this is the number of seconds between the slave
checking for updates to zones.