check behaviour with invalid notify-source-v6 address

This was reported as causing the server to fail to shutdown on
NetBSD.  Look for the expected informational and error messages.

(cherry picked from commit 580c41de0d)

bin/tests/system/notify/ns1/named.conf.in

@@ -14,6 +14,8 @@
 options {
 	query-source address 10.53.0.1;
 	notify-source 10.53.0.1;
+	# invalid notify-source-v6 address
+	notify-source-v6 fd92:7065:b8e:fffe::a35:5;
 	transfer-source 10.53.0.1;
 	port @PORT@;
 	pid-file "named.pid";

bin/tests/system/notify/ns1/root.db

@@ -19,6 +19,9 @@ $TTL 300
 				)
 .			NS	a.root-servers.nil.
 a.root-servers.nil.	A	10.53.0.1
+; sends NOTIFY using invalid notify-source-v6 address
+.			NS	other.root-servers.nil.
+other.root-servers.nil.	AAAA	fd92:7065:b8e:fffe::a35:4
 
 example.		NS	ns2.example.
 ns2.example.		A	10.53.0.2

bin/tests/system/notify/tests.sh

@@ -98,6 +98,12 @@ END {
 }' ns2/named.run >awk.out.ns2.test$n || ret=1
 test_end
 
+# See [GL#4689]
+test_start "checking server behaviour with invalid notify-source-v6 address"
+grep "zone ./IN: sending notify to fd92:7065:b8e:fffe::a35:4#" ns1/named.run >/dev/null || ret=1
+grep "dns_request_create: failed address not available" ns1/named.run >/dev/null || ret=1
+test_end
+
 nextpart ns3/named.run >/dev/null
 
 sleep 1 # make sure filesystem time stamp is newer for reload.