+5405. [bug] 'named-checkconf -p' could include spurious text
+ in server-addresses statements due to an uninitialized
+ DSCP value. [GL #1812]
+
5404. [bug] 'named-checkconf -z' could incorrectly indicate
success if errors were found in one view but not in a
subsequent one. [GL #1807]
};
zone-statistics no;
};
+ zone "example3" {
+ type static-stub;
+ server-addresses {
+ 1.2.3.4;
+ };
+ };
zone "clone" {
in-view "first";
};
clone IN first master
example1 IN second master
example2 IN second static-stub
+example3 IN second static-stub
clone IN second in-view first
. IN second redirect
clone IN third in-view first
status=`expr $status + $ret`
n=`expr $n + 1`
-echo_i "check that named-checkconf -l print out the zone list ($n)"
+echo_i "check that named-checkconf -l prints out the zone list ($n)"
ret=0
$CHECKCONF -l good.conf |
grep -v "is not implemented" |
CHECK(cfg_create_obj(pctx, type, &obj));
CHECK(cfg_parse_rawaddr(pctx, flags, &netaddr));
isc_sockaddr_fromnetaddr(&obj->value.sockaddr, &netaddr, 0);
+ obj->value.sockaddrdscp.dscp = -1;
*ret = obj;
return (ISC_R_SUCCESS);
cleanup: