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 4f0hTn6RKqz2yBj for ; Tue, 27 Jan 2026 10:29:17 +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 "R12" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4f0hTc1P8hz2xdr for ; Tue, 27 Jan 2026 10:29:08 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4f0hTb0P7Wz5hf for ; Tue, 27 Jan 2026 10:29:06 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1769509747; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=9PjxIw970DD1wR2PqWXcfjM0GXVcTpv+XI4x49ETEak=; b=1LmhbHqn3RET85gBNeZoOwSffNcO0kMkJsGxXgKTeq1Exf0SHVCNQVFBvQRXty8PKX/pJx hZ8QupcmAvg/4ZDQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1769509747; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=9PjxIw970DD1wR2PqWXcfjM0GXVcTpv+XI4x49ETEak=; b=Ee1Qj4JdOjmQ7s/P8193MzX+2qXKJnFshCX2R1chACEf1wCCzwctew4vmRl1I8JvGsQzEh britHnxJqmqinF32DxQ9Z8rpfH32U+WQGX+cDBSL8P8/dYcd/ktI9Pt6d7FO76b4k1PHld kDK3Fp5io2dWyU5dsiWcWpJT2q+5FcsYTWjVK7NdjY+u50xrodf3oY5qEGNfBVamPWQWjH at2jkUTm2lLB/F7mhEqWQSGsZ+qOOtf3gXHfha5rRw0tpxVh87o7xPQaPT5w/Kgu2QhYoD XFnpRVZXS5b8D4iEBkdOZ8oJ1E05gX4ddEXrVGiJwLXaul/9zZen5uZtjKykqQ== Message-ID: <2223b09a-31a9-4dc8-89a6-d57ed417c4ba@ipfire.org> Date: Tue, 27 Jan 2026 11:28:55 +0100 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Content-Language: en-GB To: "IPFire: Development-List" From: Adolf Belka Subject: Problem experienced with IPFire Recursor mode Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi All, Thought I would communicate about a problem I have been having. I needed to login to my Insurance web site. I could access all the web pages I wanted but when trying to login I always got a 503 not available or a timeout. This was happening for the last three days. I disabled the web proxy, IPS and the IP Blocklists functions but none of it made any difference. Also cleared all caches I could find. No difference. All other web sites and logins worked fine. This morning looking through various logs I found the following message. INFO: Unable to resolve A/AAAA record of queried destination 'auth.opgroen.nl', returning ERR... I was using the Recursor mode with my IPFire DNS but I still had 5 DNS servers listed, just not enabled. I therefore enabled them and immediately I was able to get the login screen to display. I then reverted back to the recursor mode and the login stayed worked. Also after waiting 5 minutes. I then cleared the browser cache and the login page failed to be found. I then enabled just one DNS server - recursor01.dns.lightningwirelabs.com - on the DNS page and the login page worked again. Also tested clearing the browser cache and the login page still being shown. Working now for over 15 minutes. That is compared to not working at all once over the last three days trying numerous times. So there seems to be something about my insurance providers login page that doesn't want to work well with the Recursor Mode, although everything else has worked fine. So I now have a selected DNS site and thankfully I am able to access the login page again but thought I would let you know what I found. Regards, Adolf.