Re: Problem resolving a domainkey TXT record

Hi Danilo, it is not a problem on your end, Their servers break the DNS protocol and don't respond to unknown names: $ dig +tries=1 -4 IN NS @nstll.eulisa.europa.eu ${RANDOM}.eulisa.europa.eu ;; communications error to 194.126.110.49#53: timed out ; <<>> DiG 9.21.3-1+0~20241211.133+debian12~1.

Problem resolving a domainkey TXT record

Hello, I recently noticed that emails from somewhat trustworthy organization don't have a valid DKIM signature - or rather, my email client can't verify them, because there is a timeout resolving the domainkey record. Testing this with 'dig' confirms the problem: dig txt eulisa._domainkey

query failed (SERVFAIL) and query failed (failure)

I have been using named-chroot on Fedora 40 for a long time without issue on version bind-9.18.28-2.fc40.x86_64. I have built a new router based on Fedora 41 and named version is bind-9.18.30-1.fc41.x86_64. This version is reporting errors like these: client @0x7fb312835168 172.17.1.173#62806 (b

Re: New BIND releases are available: 9.18.32, 9.20.4, 9.21.3

Hi, it's in the following directory on the link you sent: 08383792-isc-bind-bind/ 2024-Dec-12 11:59:56-- Directory More precisely: https://download.copr.fedorainfracloud.org/results/isc/bind/epel-9-x86_64/08383792-isc-bind-bind/. Let us know if "dnf update --refresh" does not work fo