From 9e345fa488a4f476114e8f1058d5d1a9c0a0ea16 Mon Sep 17 00:00:00 2001 From: Ryan Malloy Date: Wed, 20 May 2026 16:28:50 -0600 Subject: [PATCH] Corefile: drop explicit cache 30, use plugin default (3600) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The cache 30 directive in the (common) snippet was clamping authoritative TTLs to 30s max — every record HE pulled showed TTL≈5 because the cache plugin intercepts responses regardless of source (auto plugin authoritative answers AND forward plugin resolver answers). Switching to bare 'cache' uses the plugin's 3600s default, which preserves our source TTLs: most records at 300s, _dmarc/dkim/SRV at 3600s, wildcards at 60s. --- Corefile | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Corefile b/Corefile index 406eda5..feaf111 100644 --- a/Corefile +++ b/Corefile @@ -27,7 +27,11 @@ forward . 1.1.1.1 1.0.0.1 9.9.9.9 { max_concurrent 1000 } - cache 30 + # Use default cap (3600). Earlier `cache 30` clamped authoritative + # TTLs too aggressively — every record HE pulled showed TTL≈5 because + # the cache plugin sits in the (common) plugin chain and clamps any + # response passing through, not just forwarded-resolver answers. + cache errors log loop