From: Colin Vidal Date: Wed, 24 Jun 2026 16:52:41 +0000 (+0200) Subject: Fix RRL random failure X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=49cb99bb08363dcf19b15af49a53c77814461f8d;p=thirdparty%2Fbind9.git Fix RRL random failure RRL test were randomly failing because `ns2` hint files uses ``` . NS ns1. ns1. A 10.53.0.1 ``` Whereas `ns1` root zone didn't contains `ns1.` as NS (but only `ns.`). This is a problem with the following scenario: - A query starts before priming; - It gets the root hints as zonecut (with `. NS ns1.`, and no glues, this is how parent-centric currently works); - Priming starts and complete (so now rootdb contains the answer/glues from `ns1` root file); - Then the query go to ADB to resolve `ns1.`. Resolution of `ns1.` fails since it doesn't exists from the rootdb anymore. This is a configuration issue (the resolver behavior is correct and expected) whch is now fixed. --- diff --git a/bin/tests/system/rrl/ns1/root.db b/bin/tests/system/rrl/ns1/root.db index 7c5e7935d21..763261c70bc 100644 --- a/bin/tests/system/rrl/ns1/root.db +++ b/bin/tests/system/rrl/ns1/root.db @@ -1,8 +1,7 @@ $TTL 120 -@ SOA ns. hostmaster.ns. ( 1 3600 1200 604800 60 ) -@ NS ns. -ns. A 10.53.0.1 -. A 10.53.0.1 +@ SOA ns1. hostmaster.ns1. ( 1 3600 1200 604800 60 ) +@ NS ns1. +ns1. A 10.53.0.1 ; limit responses from here tld2. NS ns.tld2.