On 20.05.21 17:22, Manish Rane wrote:
> Hi Team,
>
> Are those new versions available in Linux distro packages?
As Anand already wrote: our Enterprise releases won't have this atm,
unless you request it through the official channels.
OpenSUSE Tumbleweed will hopefully have in a few days.
Josef
If you can have BIND log directly to a file, couldn't you use a FIFO
(prwxrwxrwx) or Unix domain socket (srwxrwxrwx) and avoid the disk I/O by
sending the log data directly to the forwarder? (E.g., Pulse Audio listens on a
socket for audio data from an application, and sends it in real-time to
On 20/05/2021 23:34, John Thurston wrote:
Hi John,
> My subsequent read of the docs indicates that BIND on CentOS 7, while
> being told it is sending to 'syslogd', is sending to 'journald' which is
> handling all the messages and forwarding them on to 'syslogd'. I don't
> want journald handling
Many years ago, when we ran ISC BIND on Solaris, we created a logging
channel to send the logged-queries to the local syslogd. We then had our
local syslogd forward most of the traffic on to a central syslog server.
I just tried to re-implement something like that on CentOS, and thought
I had
Thanks for the reply
--
Thanks and Regards,
Manish R
On Thu, May 20, 2021 at 9:15 PM Anand Buddhdev wrote:
> On 20/05/2021 17:22, Manish Rane wrote:
>
> > Are those new versions available in Linux distro packages?
>
>
Well, yes, that’s why the default was reverted. There’s a bug in the feature,
and there’s already MR fixing it. Sorry for the inconvenience.
If anybody is willing to test the fix, I would be happy to point them towards
the MR (and patch).
Ondrej
--
Ondřej Surý — ISC (He/Him)
My working hours
On 20/05/2021 18:08, Klaus Darilion wrote:
Hi Klaus,
> Nevertheless I think there is a bug. IIR the previous default was
> 100% (switch to AXFR if IXFR would be grater than AXFR) and we also saw
> plenty of AXFR although the IXFR difference was very small and far away
> from 100%
Yes, I agree.
Nevertheless I think there is a bug. IIR the previous default was 100% (switch
to AXFR if IXFR would be grater than AXFR) and we also saw plenty of AXFR
although the IXFR difference was very small and far away from 100%
regards
Klaus
> -Ursprüngliche Nachricht-
> Von: bind-users Im
On 5/20/21 8:43 AM, Anand Buddhdev wrote:
> On 20/05/2021 15:30, Tim Daneliuk via bind-users wrote:
>
> Hi Tim,
>
>> Recently - and for no obvious reason - the on-prem instance stops resolving
>> properly. The fix is to stop it, clear out the slave files, and restart.
>> Then it works for a few
On 20/05/2021 17:22, Manish Rane wrote:
> Are those new versions available in Linux distro packages?
Bleeding-edge distros like Gentoo Linux will probably have packages
within a short time. If you use Homebrew on your system, you'll also
have the newest version soonish.
Most of the major
Hi Team,
Are those new versions available in Linux distro packages?
--
Thanks and Regards,
Manish R
On Thu, May 20, 2021 at 8:08 PM Anand Buddhdev wrote:
> On 20/05/2021 00:06, Michael McNally wrote:
>
> Hi ISC people,
>
On 20/05/2021 00:06, Michael McNally wrote:
Hi ISC people,
> RELEASE-NOTES-bind-9.16.16.html
I was just reading the release notes, and noticed:
"The default value of the max-ixfr-ratio option was changed to
unlimited, for better backwards compatibility in the stable release series."
Thank you
On 20/05/2021 15:30, Tim Daneliuk via bind-users wrote:
Hi Tim,
> Recently - and for no obvious reason - the on-prem instance stops resolving
> properly. The fix is to stop it, clear out the slave files, and restart.
> Then it works for a few days and repeats its misbehavior.
>
> The logs show
Running bind 9.16.15 on FreeBSD 11.4-STABLE.
Master is out on a cloud server at Digital Ocean. Slave is on-premise.
All on-prem LANs point to the slave instance.
Running split horizon to keep nosey parkers out of our local DNS assignments.
Recently - and for no obvious reason - the on-prem
14 matches
Mail list logo
