checkpoint: multiple-DLZ functionality
- multiple DLZ's can be specified, including multiple DLZ's using the same driver; e.g., two different back-ends both loaded by the dlopen driver - new "search" option can be specified in a DLZ indicating whether this DLZ database should be searched for unknown zones. The default is "yes". If "no", then the zone can only be found by named if it's registered in the zone table, which happens if the zone is configured for dynamic updates, or if "dlz <dlzname>" is specified in the zone statement. (The latter functionality is incomplete in this commit).
This commit is contained in:
@@ -70,4 +70,21 @@ done
|
||||
[ "$ret" -eq 0 ] || echo "I:failed"
|
||||
status=`expr $status + $ret`
|
||||
|
||||
echo "I:testing multiple DLZ drivers"
|
||||
test_update testdc1.alternate.nil. A "86400 A 10.53.0.10" "10.53.0.10" || ret=1
|
||||
status=`expr $status + $ret`
|
||||
|
||||
echo "I:testing AXFR from DLZ drivers"
|
||||
$DIG $DIGOPTS +noall +answer axfr example.nil > dig.out.ns1.1
|
||||
n=`cat dig.out.ns1.1 | wc -l`
|
||||
[ "$n" -eq 7 ] || ret=1
|
||||
$DIG $DIGOPTS +noall +answer axfr alternate.nil > dig.out.ns1.2
|
||||
n=`cat dig.out.ns1.2 | wc -l`
|
||||
[ "$n" -eq 5 ] || ret=1
|
||||
status=`expr $status + $ret`
|
||||
|
||||
echo "I:testing unsearched DLZ driver"
|
||||
$DIG $DIGOPTS +noall +answer ns other.nil > dig.out.ns1.3
|
||||
cat dig.out.ns1.3
|
||||
|
||||
exit $status
|
||||
|
||||
Reference in New Issue
Block a user