Re: Query on issue#2389 BIND 9.16.10

BIND 9.16.10 was tagged and released in December 2020. That’s almost a year ago. You can’t and should not expect people do work for free when you slacked on updates. You have to carry the costs of the bad decision you made when you decided to stick with old version. The word “free” in free softw

RE: Query on issue#2389 BIND 9.16.10

Hi Ondrej This issue is becoming a ripple effect for us and on the path of becoming a blocker. I agree with you that same question should not be asked on different channels. Being seeing the gravity of the issue, the query may have been posted on different channels by different teams to get the

Query on issue#2389 BIND 9.16.10

People, just don’t do this: https://gitlab.isc.org/isc-projects/bind9/-/issues/2958 If you don’t get answer you like via one channel asking the exactly question via different channel will not only get you the answer it also shows that you are disrespectful. Generally, we are happy to help, bu

Re: Query on issue#2389 BIND 9.16.10

People, just don’t do this: https://gitlab.isc.org/isc-projects/bind9/-/issues/2958 If you don’t get answer you like via one channel asking the exactly question via different channel will not only get you the answer it also shows that you are disrespectful. Generally, we are happy to help, but

Re: Query on issue#2389 BIND 9.16.10

Am 19.10.21 um 00:46 schrieb raf: On Mon, Oct 18, 2021 at 01:02:07PM +0200, Reindl Harald wrote: Am 18.10.21 um 12:57 schrieb Rajnish Kamboj via bind-users: Upgrading to latest release will fix the issue lesson to learn: report issues after you made sure you are using the latest version

Re: Query on issue#2389 BIND 9.16.10

On Mon, Oct 18, 2021 at 01:02:07PM +0200, Reindl Harald wrote: > Am 18.10.21 um 12:57 schrieb Rajnish Kamboj via bind-users: > > Upgrading to latest release will fix the issue > > lesson to learn: report issues after you made sure you are using the latest > version which probably would fix it >

Re: Query on issue#2389 BIND 9.16.10

All the information available is always written down in the issue you have already referenced. That’s always the case - even with security issues, there’s only 1 month+ delay to give people chance to upgrade. Ondřej -- Ondřej Surý — ISC (He/Him) My working hours and your working hours may be di

Re: Query on issue#2389 BIND 9.16.10

Am 18.10.21 um 12:57 schrieb Rajnish Kamboj via bind-users: Upgrading to latest release will fix the issue lesson to learn: report issues after you made sure you are using the latest version which probably would fix it Can you also help us with scenarios as to why this issue is occurring?

RE: Query on issue#2389 BIND 9.16.10

Thanks Ondrej for your quick reply, Upgrading to latest release will fix the issue. Can you also help us with scenarios as to why this issue is occurring? May be this will help us in quick workaround (if possible) till the time we plan for latest BIND. Regards Rajnish Kamboj -Original Mess

Re: Query on issue#2389 BIND 9.16.10

Hi, there were several security issues since 9.16.10, you should be running either last 9.16.x release (9.16.21 as of time writing this email) or have all of the issues patched. The thing you are asking for is so wrong on so many levels. Don’t do that, upgrade to last version instead. Ondrej --

Query on issue#2389 BIND 9.16.10

Hi Team, Currently we are using Bind version 9.16.10, My Query I recently found that there is an issue with the 9.16.10 version. "Issue#2389 BIND 9.16.10: critical: xfrout.c:1643: INSIST(xfr->sends == 0) failed". Can anyone please help me to understand the scenario when this issue will appear?