On 2/16/22 17:50, Grant Taylor via bind-users wrote:
Most of the -- what I'll call -- binary distributions of Linux tend to
have a fairly small range of any given versions of software in the
repositories provided by the Linux distribution provider.
There is nothing that prevents you from so
On 2/16/22 17:18, Timothe Litt wrote:
You can get IPv6 via a tunnel broker. Hurricane Electric
(http://he.net/) is one of the larger ones. You can get a /48 from
them - for free. Bandwidth is modest. You can setup reverse zones;
they'll delegate. I don't think they support DNSSEC - it's
On 2/16/22 17:15, Borja Marcos wrote:
Now I have 9.11.36, 9.16.24 and 9.18.0
What I have noticed with 9.18.0, which is running on the heaviest loaded
server, is less memory footprint.
I started it on Monday and according to top it’s taking 486 MB (SIZE) - 375 MB
(RES). And the memory press
On 2/16/22 15:49, Reindl Harald wrote:
not when you don't use 3rd party repos or build it at your own - the
whole point of a stable distibution is to not have random
major-upgrades of software
and unless you have no very good reason you should either stay at the
packages from your distr
On 2/16/22 14:38, Andrew Baker via bind-users wrote:
Firstly, we are running bind 9.11 on Debian 10 hosts.
* Is it worth use upgrading to Debian 11 to get the newer version of
bind?
I don't run Linux, but shouldn't it be possible to just upgrade only
BIND on your current Linux relea
Hi all.
Just coming back to this...
I notice that the release notes for 9.16.25 say the memory leak issue on
FreeBSD is now fixed:
*
On FreeBSD, TCP connections leaked a small amount of heap memory,
leading to an eventual out-of-memory problem. This has been fixed in:
https://gitlab.i
On 2/15/22 09:06, Andrew Baker via bind-users wrote:
Dear List,
We are based in the middle east and manage a lot of domains across a
lot of tld’s including regional ones. Not all registrars are equal and
the DNS services of several weren’t offering what we required. For a
number of operat
On 9/13/21 09:40, Ondřej Surý wrote:
Hi,
if you have reliable reproducer, please fill an issue at
https://gitlab.isc.org/isc-projects/bind9/-/issues
While this mailing list is monitored by the BIND 9 team, it’s more practical to
have an issue filled by
a person experiencing the problem wher
On 9/13/21 09:12, Borja Marcos wrote:
2- Adding a bogus 127.10.whatever to the spare Ethernet interface I am not
using, per a previous comment on
this thread about a memory leak due to interfaces with no addresses.
This issue does need to get fixed. Assigning random, unused IP addresses
to
On 9/10/21 12:35, sth...@nethelp.no wrote:
Freebsd 12.2-STABLE here with servers running BIND 9.16.15, 9.16.18
and 9.16.20, all using libuv 1.41.0, all installed from ports. Typical
query load from around 3k qps to around 14k qps. No sign of any memory
leak.
Would be interesting to hear you
On 9/10/21 10:29, Borja Marcos wrote:
Which version of libuv are you using? I am running 1.41 and the latest is 1.42.
I'm running libuv-1.41.0.
I haven’t seen that behavior and my recursives handle about 100,000 requests
per minute.
Just in case I have updated libuv on one of them.
I
2.5 days in, and 9.11 is still running good, with no crashing.
Safe to say that this memory leak is definitely an issue with 9.16.
Mark.
On 9/6/21 19:30, Mark Tinka wrote:
So I've decided to downgrade our busiest resolvers to bind911-9.11.35.
So I've decided to downgrade our busiest resolvers to bind911-9.11.35.
Mark.
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
ISC funds the development of this software with paid support subscriptions.
I'm seriously considering going back to BIND-9.11.
Mark.
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
ISC funds the development of this software with paid support subscriptions.
Contact us at https:
On 9/3/21 07:17, Mark Tinka wrote:
Let me monitor and report back. Thanks.
So since running the updated interface changes from Friday, BIND died
again due running out swap space, earlier today.
Seems like it may be more than how BIND is listening on various interfaces.
Are you able to
On 9/3/21 01:55, Michael Sinatra wrote:
'listen-on any;' is the default for v4, so you should actually be
listening on 127.0.0.1 in addition to everything else (since all of
your listen-on's for v4 appear to be commented out). You *should* be
able to remove 'listen-on-v6 { ::1; };' and j
On 9/2/21 23:51, Michael Sinatra wrote:
I have noticed this also and have opened a (similar but different)
issue, but it's a bit weird how it manifests itself.
On your freebsd installation, make sure that all of your interfaces
are configured and that bind can listen on them. (They don't
Not sure if this issue offers some clue:
https://gitlab.isc.org/isc-projects/bind9/-/issues/2575
I see its maintainer just closed it 11hrs ago...
Mark.
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this li
On 9/2/21 16:30, Michal Nowak wrote:
Mark, what's the exact BIND 9.16 version which is crashing for you?
I started off with 9.16.19 several weeks ago (coming from 9.11), and
that was crashing.
I upgraded to 9.16.20 last week, and it's crashing too.
Why do you say that the reason for cr
Hi all.
Ever since we moved from BIND-9.11 to BIND-9.16, we've been experiencing
'named' crashing after 24hrs - 36hrs on high-load resolver-only servers,
running on FreeBSD-13.0.
We found that the reason for this was due to BIND running out of swap space.
An increase in swap space by creatin
20 matches
Mail list logo
