;; ADDITIONAL SECTION:
NS.example. 172800 IN A 192.0.2.1
NS.example. 172800 IN A 192.0.2.2
-NS1.example.COM. 172800 IN A 192.0.2.101
-NS1.example.COM. 172800 IN AAAA 2001:db8::1
+NS1.example.COM. 172800 IN A 192.0.2.3
+;; These are not used now - they are in a different master file
+;; than the answer.
+; NS1.example.COM. 172800 IN A 192.0.2.101
+; NS1.example.COM. 172800 IN AAAA 2001:db8::1
"listen_on": [{"address": "10.53.0.1", "port": 53210}],
"database_file": "@abs_builddir@/zone.sqlite3"
},
+ "data_sources": {
+ "classes": {
+ "IN": [{
+ "type": "sqlite3",
+ "params": {
+ "database_file": "@abs_builddir@/zone.sqlite3"
+ }
+ }]
+ }
+ },
+ "Logging": {
+ "loggers": [
+ {
+ "name": "*",
+ "severity": "DEBUG",
+ "output_options": [],
+ "debuglevel": 99
+ }
+ ]
+ },
"Boss": {
"components": {
"b10-auth": {"kind": "needed", "special": "auth" },
example. 172800 IN NS NS1.example.COM.
NS.example. 172800 IN A 192.0.2.1
NS.example. 172800 IN A 192.0.2.2
-; this "glue" is below a zone cut for com. BIND 9 still uses it for
-; the delegation to example. BIND 10 (with sqlite3 data source) doesn't.
NS1.example.COM. 172800 IN A 192.0.2.3
;
$PERL $DIGCOMP example.good dig.out.$n || status=1
n=`expr $n + 1`
-echo "I:testing that we find glue A RRs we are authoritative for ($n)"
-$DIG +norec @10.53.0.1 -p 53210 foo.bar.example.org. a >dig.out.$n || status=1
-$PERL $DIGCOMP auth.good dig.out.$n || status=1
-n=`expr $n + 1`
+# Disabling this test, as it checks for looking up glue in a different zone
+# finder than the answer is from. This is not supported now.
+#echo "I:testing that we find glue A RRs we are authoritative for ($n)"
+#$DIG +norec @10.53.0.1 -p 53210 foo.bar.example.org. a >dig.out.$n || status=1
+#$PERL $DIGCOMP auth.good dig.out.$n || status=1
+#n=`expr $n + 1`
# We cannot do this test for BIND 10 because b10-auth doesn't act as a
# recursive (caching) server (by design)