Hi Matthew
I can confirm that this package did indeed fix the issue. The current
packaged version still presented the problem so it looks like you patch
fixed it.
I would be interested to know why compiling from upstream doesn't
present the issue however.
Thanks
--
You received this bug
Yeah testing should be no problem. I will get a server ready.
It may take me some time to get this done however.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909950
Title:
TCP connections never
Sure thing:
Upstream Build: BIND 9.16.10
Debian Distro Build: 9.11.5
I have since migrated all the affected machines to KNOT-Resolver but I
have kept one off our network with Bind9 still running if you need any
extra info.
Thanks
--
You received this bug notification because you are a member
Yes that exactly, essentially we found that we had the connections set
to 1000 and one client opened a few connections but they never closed,
they then opened more and more naturally.
In the end one client had over 900 connections. Once we hit 1000 we ran
a quick dig against the server and it
Thanks for the update.
Config files are attached. You will note that the only override we we
for TCP clients is the amount that are allowed to connect as the default
is very low for an ISP DNS server.
However we are relying on the default tcp-timeout values. I will note
that since we removed the
Public bug reported:
The default timeout for TCP connections on port 53 to named/bind9 is 300
seconds. The upstream ISC build of bind9 uses this and honors an
overrides you set in the config files.
The Ubuntu packaged version of bind9 seems to hold idle connections
forever, eventually exhausting
