From 3e7aa395774dfb23fe36a30a70b13624487d37b8 Mon Sep 17 00:00:00 2001 From: Evan Hunt Date: Thu, 6 Dec 2012 13:59:30 -0800 Subject: [PATCH] [master] minor doc fix --- doc/arm/dlz.xml | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/doc/arm/dlz.xml b/doc/arm/dlz.xml index d74bcf4eca..abe03cc736 100644 --- a/doc/arm/dlz.xml +++ b/doc/arm/dlz.xml @@ -75,24 +75,24 @@ set to yes will be queried to find out if they contain an answer for the query name; the best available answer will be returned to the client. - - - The option in the above example can be - omitted, because yes is the default value. - - - If is set to no, then - this DLZ module is not searched for the best - match when a query is received. Instead, zones in this DLZ must be - separately specified in a zone statement. This allows you to - configure a zone normally using standard zone option semantics, - but specify a different database back-end for storage of the - zone's data. For example, to implement NXDOMAIN redirection using - a DLZ module for back-end storage of redirection rules: - - + + + The option in the above example can be + omitted, because yes is the default value. + + + If is set to no, then + this DLZ module is not searched for the best + match when a query is received. Instead, zones in this DLZ must be + separately specified in a zone statement. This allows you to + configure a zone normally using standard zone option semantics, + but specify a different database back-end for storage of the + zone's data. For example, to implement NXDOMAIN redirection using + a DLZ module for back-end storage of redirection rules: + + dlz other { - database "dlopen driver.so "; + database "dlopen driver.so "; search no; };