Sami,
After you regenerate your rndc key as Mark advised, you will need to provide us
with more information, as what you've sent is not sufficient to troubleshoot
your symptom. As a first step, take a packet capture on the resolver that shows
incoming queries from the client and the correspond
Before you do anything else change your rndc shared key as you published it.
> On 14 Jun 2024, at 01:00, sami.ra...@sofrecom.com wrote:
>
> Hello community,
> We are experiencing a resolution problem: 'SERVFAIL error'. Our environment
> is BIND 9.16.48, OS: Redhat8. I am sharing with you a part
We’ve been using the ISC BIND 9 COPR repositories at
https://copr.fedorainfracloud.org/coprs/isc/ for a few years now, but I had a
question – is there a planned date to update the “bind-esv” channel to provide
BIND 9.18 rather than BIND 9.16? Since 9.16 is now EOL we’ve switched to using
the s
Investigating about non trivial RPZ configurations, I noticed a huge
block on bind 9.12 to provide DNSRPS, an API for external RPZ providers.
Nevertheless, the code is complicated and there is no documentation.
Checking around I only found a RPZ module provided by the same people
people that im
Hello community,
We are experiencing a resolution problem: 'SERVFAIL error'. Our environment is
BIND 9.16.48, OS: Redhat8. I am sharing with you a part of the log that
contains this error, named.conf file.
What I've noticed is that the resolution problem is mainly related to domain
names that
5 matches
Mail list logo