From 32c97c94c793f57892ca0922b9c5ec0800121887 Mon Sep 17 00:00:00 2001 From: Ben Vincent Date: Sun, 12 Jul 2026 22:24:53 +1000 Subject: [PATCH] Fix validate-except syntax: semicolon after last list entry The resolver validate-except list (#251) omitted the trailing semicolon after the final entry, so named fails config parse (named.conf: missing ';' before '}') and the resolver pods crash-loop. BIND requires every entry in the list to be semicolon-terminated, including the last one before the closing brace. --- apps/base/bind-internal/resolvers/cluster.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/base/bind-internal/resolvers/cluster.yaml b/apps/base/bind-internal/resolvers/cluster.yaml index 2fc2888..161a7bd 100644 --- a/apps/base/bind-internal/resolvers/cluster.yaml +++ b/apps/base/bind-internal/resolvers/cluster.yaml @@ -29,7 +29,7 @@ spec: # insecure so they are not validated. unkin.net covers all *.unkin.net # (incl. k8s.syd1.au.unkin.net); 18.198.in-addr.arpa covers every reverse zone. extraOptions: - - "validate-except { unkin.net; 18.198.in-addr.arpa; consul }" + - "validate-except { unkin.net; 18.198.in-addr.arpa; consul; }" resources: requests: cpu: 20m -- 2.47.3