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 4f0r3d3QxSz2yBj for ; Tue, 27 Jan 2026 16:10:37 +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 4f0r3Y68C4z2xM3 for ; Tue, 27 Jan 2026 16:10:33 +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 4f0r3Y0nyhz5cS; Tue, 27 Jan 2026 16:10:33 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1769530233; 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=g3gYY3tuiaU9uzLnv4YveCXYDm8NcUvBTiEIQSjf2Ww=; b=ibK6UFyhPDzM4sknKp21ZHFEcxUOo4KSG94KqSv7TbX61jIXfziVU7JNVvsWxJ7W/qB00q 88P5X2pUfqsyJ/BA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1769530233; 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=g3gYY3tuiaU9uzLnv4YveCXYDm8NcUvBTiEIQSjf2Ww=; b=WD3AqaxoOAZuVl7SALAc2XhQpN9Xn1u4I3K2aFqdXb70Gp95+xRdMcR+7rDY2hzvs78CAN dXupPzJ0Ezgc7oZNJLLit9TYqfL7f6vwoKKHNyLEYzOkLIrLslXe0LkVGkbh0Xvh5Lwnw3 lVwKDLG9PlndkXPWV2nRUJ7Jn8eZeonl9sRpuy9ekIwPsI0aTrLJP+LcygEHDY0mPtaqly mrKPE+K2BjsrTW1XK5um0FDq4NhSBdYv57m7D/Nz760fKyAf6vQwdp+V1Ua11eUT5cAWYz LD5sIiyodBlhJ3EXnLcZtw9fZdxjGpzRb3RxVO7xd1vuP69y/AncP2jYRzruyg== Content-Type: text/plain; charset=utf-8 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: Problem experienced with IPFire Recursor mode From: Michael Tremer In-Reply-To: <2223b09a-31a9-4dc8-89a6-d57ed417c4ba@ipfire.org> Date: Tue, 27 Jan 2026 16:10:32 +0000 Cc: "IPFire: Development-List" Content-Transfer-Encoding: quoted-printable Message-Id: <533CB0E0-EB46-45B4-ADB6-E5654D4A8F1B@ipfire.org> References: <2223b09a-31a9-4dc8-89a6-d57ed417c4ba@ipfire.org> To: Adolf Belka Hello Adolf, Interesting case. I tried to resolve the domain at my office and that = seems to be working just fine. They don=E2=80=99t even use DNSSEC, so any problems from that can be = ruled out. Anything more in the logs? It could have been the IP blocklists blocking = communication. If you have been testing DBL, that can probably be ruled out because you = don=E2=80=99t resolve anything. The domain is not listed: = https://www.ipfire.org/dbl/search?q=3Dauth.opgroen.nl -Michael > On 27 Jan 2026, at 10:28, Adolf Belka wrote: >=20 > Hi All, >=20 > Thought I would communicate about a problem I have been having. >=20 > 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. >=20 > 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. >=20 > This morning looking through various logs I found the following = message. >=20 > INFO: Unable to resolve A/AAAA record of queried destination = 'auth.opgroen.nl', returning ERR... >=20 > 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. >=20 > 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. >=20 > I then enabled just one DNS server - = recursor01.dns.lightningwirelabs.com - on the DNS page and the login = page worked again. >=20 > Also tested clearing the browser cache and the login page still being = shown. >=20 > Working now for over 15 minutes. That is compared to not working at = all once over the last three days trying numerous times. >=20 > 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. >=20 > 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. >=20 > Regards, >=20 > Adolf. >=20 >=20