From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4h5QGt1Kfvz34b7 for ; Thu, 23 Jul 2026 09:06:46 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (secp384r1 raw public key) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "YR2" (not verified)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4h5QGp5hbNz2xSl for ; Thu, 23 Jul 2026 09:06:42 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4h5QGp0CVDz3MV; Thu, 23 Jul 2026 09:06:41 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1784797602; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=u+qFSZK8Sbbe4BmOWz+3q2299gbTw34V8Sg9ULjxltw=; b=siQGGWU5kzAzigHMH06KcMj5MIWTtIcy3WoYQIzlc8fPKPqO/TioGKOjUAhf8M2CmWMa5H /CeEqMVh8sCL19DA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1784797602; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=u+qFSZK8Sbbe4BmOWz+3q2299gbTw34V8Sg9ULjxltw=; b=hM2lpzkgUUBCTTt5CqW32OGcYQyXmsHjObyrEYBhscpK96cgruKjGc6G42V6wz7ge+KFXB 1mmfPFe9Jpbry99d8jc5zveomWbx8VWX996SDWn3AbHtf04xLX08PiNLvtippBHjQDpDpz /ejA1ihaIQoDW0YXsVSwJ5zpZqtkhXtkhZ0DHiS2rK9j2x4KXE5OodgdQTrQOitG0f1sWv PoTtGYc+syjkMjBn3hb13CPk+cH8WS9bTQQTG4k71XPWDX1cPrwJ780qmvs2byEi4qBJkl beqMSV6F7uXt0sIqMI1CWG9+wbuZmh4AtGiOq16Fw5D4aeiAZBlDvFJM2aMQBQ== Content-Type: text/plain; charset=us-ascii Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: Core 203 - DNS firewall doesn't update (?) or add (!) - zone files From: Michael Tremer In-Reply-To: <249cfa40-47dc-4a9a-9b8b-0e02933d4f34@cox.net> Date: Thu, 23 Jul 2026 10:06:41 +0100 Cc: development@lists.ipfire.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <6662cba6-6773-4040-ace7-7be7f8ad3679@ipfire.org> <249cfa40-47dc-4a9a-9b8b-0e02933d4f34@cox.net> To: Mentalic Hello Wayne, There are currently no confirmed reports about the DNS firewall not = working. If you are experiencing a problem, please provide log files, = what you did to debug it and potentially open a bug report with all = information. All the best, -Michael > On 22 Jul 2026, at 14:28, Mentalic wrote: >=20 > Hi, >=20 > I can verify that the DNS firewall is not working in 203. Ended up = going back to 202. >=20 >=20 > Regards >=20 > Wayne >=20 > On 7/22/2026 8:02 AM, Matthias Fischer wrote: >> Hi, >>=20 >> I have one problem with Core 203 and I'm not sure whats the culprit: >>=20 >> No matter what I do, Core 203 won't download additional zone files. >>=20 >> After rebooting I found the already used and activated blocklists = (from >> Core 202) in the '/var/lib//knot-resolver/zones' dirextory. They're >> working - no seen problem. But even if I activate them all on the = DNSBL >> page, nothing gets downloaded, the selection and number of block = lists >> always remain the same. It won't add or remove any of the existing = lists. >>=20 >> Can anyone confirm? OR give me a hint where to look at? >>=20 >> Thanks in advance >> Matthias >>=20 >>=20 >=20