On 6/3/21 7:05 PM, Peter via bind-users wrote:
Guess not even a subscription will not happen too.
I'm having to try and do Bind on ubuntu and it just will not let me
edit files like named.conf unless you do some vodoo that I don't
understand and even updating the bind like how? Windows no
On 6/3/21 2:17 PM, Reindl Harald wrote:
Am 03.06.21 um 20:12 schrieb Danny Mayer via bind-users:
I don't speak for ISC but it's important to understand that support
of an operating system costs money and unless a company or
organization is willing to step up with money it cannot be
I am sorry, but I don’t follow. The catch is that the Windows support must be
maintained for any new development and it doesn’t come for free. Sometimes we
can’t even use what we need because there’s no support on Windows.
As an example - we are replacing the internal memory allocator with
Am 03.06.21 um 20:12 schrieb Danny Mayer via bind-users:
I don't speak for ISC but it's important to understand that support of
an operating system costs money and unless a company or organization is
willing to step up with money it cannot be expected to continue support.
There was
I don't speak for ISC but it's important to understand that support of
an operating system costs money and unless a company or organization is
willing to step up with money it cannot be expected to continue support.
There was originally a need and the money for BIND9 on Windows which is
why
Thanks Vicky and Ondrej for providing clarity. I'll be sad to see it when this
happens but as I said in my original post I don't underestimate the sheer
amount of effort required to maintain BIND for Windows going forwards so it's
completely understandable that you want to focus on platforms
Lol. End Of The Road. Queue boys 2 men...
https://g.co/kgs/8G4XvF
On Wed, Jun 2, 2021, 16:10 Victoria Risk wrote:
> > On Jun 2, 2021, at 3:24 PM, Peter via bind-users <
> bind-users@lists.isc.org> wrote:
> >
> > Well that sucks no more bind for windows...:(
>
> We are supporting BIND 9.16
> On Jun 2, 2021, at 3:24 PM, Peter via bind-users
> wrote:
>
> Well that sucks no more bind for windows...:(
We are supporting BIND 9.16 on Windows, and we are supporting 9.16 through the
end of 2024, so we are not at the end of the road yet!
https://kb.isc.org/docs/aa-00896
Vicky
> On Jun 2, 2021, at 1:36 PM, Richard T.A. Neal wrote:
>
> Could I ask if a conclusion has been reached regarding this? I know there was
> quite a bit of chatter in April/May but it's not clear to me whether any
> conclusions were reached.
We are pretty well decided that we will not support
Hi Richard,
the current plan is to keep the Windows support for the lifetime of the 9.16
branch and then when 9.16 reaches-end-of-life do a snapshot of the last release
and cherry-pick `dig.exe` into separate download because it was mentioned
multiple times that people would like to keep dig
Could I ask if a conclusion has been reached regarding this? I know there was
quite a bit of chatter in April/May but it's not clear to me whether any
conclusions were reached.
If 9.16 is to be the last officially supported Windows version then have you
decided yet which features from 9.17
I didn't think you were blaming anyone. I was just explaining the
history though my work on it largely stopped after 2008-9.
Danny
On 5/13/21 1:14 PM, Ondřej Surý wrote:
Danny,
I didn’t write the email to put the blame anywhere or point fingers. I am just
describing the situation.
Ondřej
Danny,
I didn’t write the email to put the blame anywhere or point fingers. I am just
describing the situation.
Ondřej
--
Ondřej Surý — ISC (He/Him)
My working hours and your working hours may be different. Please do not feel
obligated to reply outside your normal working hours.
> On 13. 5.
On 5/13/21 9:45 AM, Ondřej Surý wrote:
Hey,
just a follow-up with a recent real life example.
I’ve spent few days hunting a problem on Windows that got introduced by a fix
to outgoing UDP selection code. While having bugs in normal (and this was
really one-liner), it’s abnormal to not have
Hey,
just a follow-up with a recent real life example.
I’ve spent few days hunting a problem on Windows that got introduced by a fix
to outgoing UDP selection code. While having bugs in normal (and this was
really one-liner), it’s abnormal to not have tools for debugging the problem.
Here’s
On 5/10/21 5:11 AM, Ondřej Surý wrote:
On 10. 5. 2021, at 10:29, Richard T.A. Neal wrote:
At this time I don't therefore believe that running BIND via WSL or WSL2 on
Windows Server is a viable reliable solution.
Thanks for the analysis.
The alternative is as I outlined in the first email,
> On 10. 5. 2021, at 10:29, Richard T.A. Neal wrote:
>
> At this time I don't therefore believe that running BIND via WSL or WSL2 on
> Windows Server is a viable reliable solution.
Thanks for the analysis.
The alternative is as I outlined in the first email, somebody needs to step up
and
I spent some time last week looking at options for running BIND under WSL on
Windows Server. Unfortunately it doesn't presently look like a viable solution
for the following reasons:
There are two versions of WSL: WSL1 and WSL2. Development has all but ceased on
WSL1, but WSL1 is the only
Robert M. Stockmann wrote:
>
> Does bind 9 need C11 atomics ?
Yes. BIND used to have its own atomic implementation but that kind of code
is tricky and arcane, so it's better to use the standard implementations
in the C library.
It is not just a matter of the hardware BIND runs on: atomics rely
On Thu, 29 Apr 2021, [utf-8] OndÅej Surý wrote:
> Date: Thu, 29 Apr 2021 13:35:32 +0200
> From: "[utf-8] OndÅej Surý"
> To: BIND Users
> Subject: Deprecating BIND 9.18+ on Windows (or making it community
> improved and supported)
>
> Hi,
>
> we've been discussing the /subj for quite
I would personally be very sad to see the end of BIND for Windows, but I don’t
underestimate the challenges the ISC Team has in maintaining it.
Unfortunately I'm a VB.NET hobbyist programmer rather than a C/C++ developer so
I can't speak to the usefulness of the following statement, but the
> On 29. 4. 2021, at 15:42, Timothe Litt wrote:
>
> Would reducing support to just the diagnostic tools be a helpful middle
> ground?
Not really. The tools use the same internal libraries for networking. And it
would bring more complexity and not less complexity.
There’s no middle ground -
On 29 Apr 2021, at 05:35, Ondřej Surý wrote:
> * Windows now has WSL2
> (https://docs.microsoft.com/en-us/windows/wsl/install-win10) that can be used
> to run BIND 9 natively
I'd suggest this be the first listed reason as it pretty much makes all the
other reasons irrelevant. OTOH, I don't
I gave up on running named on Windows long ago, so I generally support
this direction.
However, I do use the diagnostic tools (dig, delv, rndc, nsupdate) for
troubleshooting. It can be helpful to diagnose from the client
environment (e.g. thru the same firewalls, anti-virus, buggy network
stack,
24 matches
Mail list logo
