Commit 47c41400b5 for bind

commit 47c41400b5a9bf7689bf8599b88c80ebda326739
Author: Ondřej Surý <ondrej@isc.org>
Date:   Sun Oct 11 13:43:22 2026 +0200

    Align the checkconf root KSK cutoff with named-checkconf

    named-checkconf keeps warning about a root trust anchor that has only
    the 2026 KSK until 23:59 UTC on 11 October 2026, but the checkconf
    test switched to expecting no warning at 00:00 UTC on that day.  For
    that one day every pipeline failed the checkconf test.  Use the same
    cutoff as the checker.

    Assisted-by: Claude:claude-fable-5-1

diff --git a/bin/tests/system/checkconf/tests.sh b/bin/tests/system/checkconf/tests.sh
index 2352b59cc2..3fae8e4499 100644
--- a/bin/tests/system/checkconf/tests.sh
+++ b/bin/tests/system/checkconf/tests.sh
@@ -588,7 +588,7 @@ status=$((status + ret))
 # By 23:59 11 October 2026 the IANA root zone should be being signed with the
 # 2026 trust anchor.  Prior to that check that we are warning that we are
 # missing the 2017 trust anchor.
-if test $(date +%s) -lt 1791676800; then
+if test $(date +%s) -lt 1791763140; then
   n=$((n + 1))
   echo_i "check that the 2026 ICANN ROOT KSK alone generates a warning ($n)"
   ret=0