Well for the time being I give up I think something like this happen
before many years ago, I'm sure someone will post having this iusse.
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
ISC funds the d
kconf and execute it properly
From: bind-users on behalf of Peter via
bind-users
Sent: Saturday, June 19, 2021 8:47 PM
To: bind-users@lists.isc.org
Subject: Re: Windows support has been discontinued in BIND 9.17+ (Was:
Important: A significant flaw is prese
2021 7:48 pm
> To: bind-users@lists.isc.org
> Subject: Re: Windows support has been discontinued in BIND 9.17+ (Was:
> Important: A significant flaw is present in June BIND releases 9.16.17 and
> 9.17.14)
>
> I getnothing which means good? installed back to the default path.
>
present in June BIND releases 9.16.17 and
9.17.14)
I getnothing which means good? installed back to the default path.
C:\Program Files\ISC BIND 9\bin>named-checkconf
C:\Program Files\ISC BIND 9\bin>
On 19/06/2021 5:53 pm, Richard T.A. Neal wrote:
And what do you get when you run c:\BIND
I getnothing which means good? installed back to the default path.
C:\Program Files\ISC BIND 9\bin>named-checkconf
C:\Program Files\ISC BIND 9\bin>
On 19/06/2021 5:53 pm, Richard T.A. Neal wrote:
And what do you get when you run c:\BIND\named-checkconf ?
Richard.
_
And what do you get when you run c:\BIND\named-checkconf ?
Richard.
From: bind-users On Behalf Of Peter via
bind-users
Sent: 19 June 2021 3:41 pm
To: bind-users@lists.isc.org
Subject: Re: Windows support has been discontinued in BIND 9.17+ (Was:
Important: A significant flaw is present in
Re: Windows support has been discontinued in BIND 9.17+
(Was: Important: A significant flaw is present in June BIND releases
9.16.17 and 9.17.14)
It shows 17 information with the last showing "using 1 UDP listener
per interface" maybe it don't like my intel VLAN's?
__
tion 'x'
C:\BIND\etc\named.conf:8: unexpected token near end of file
Richard.
From: bind-users On Behalf Of Peter via
bind-users
Sent: 18 June 2021 5:49 pm
To: bind-users@lists.isc.org
Subject: Re: Windows support has been discontinued in BIND 9.17+ (Was:
Important: A significant
It shows 17 information with the last showing "using 1 UDP listener per
interface" maybe it don't like my intel VLAN's?
On 18/06/2021 5:21 pm, Richard T.A. Neal wrote:
When you say “in Application logs show fine” – how far does named
actually get (if at all)? For example whenever I (re)start
ts.isc.org
Subject: Re: Windows support has been discontinued in BIND 9.17+ (Was:
Important: A significant flaw is present in June BIND releases 9.16.17 and
9.17.14)
I go back to BIND 9.17.12 and is starts fine install BIND 9.16.18 changed log
on to “local system account” like I have done for years g
I go back to BIND 9.17.12 and is starts fine install BIND 9.16.18
changed log on to “local system account” like I have done for years go
to start BIND get error 1067 in:
system logs
The ISC BIND service terminated unexpectedly. It has done this 1
time(s). The following corrective action will
Neither can we. Testing the Windows release is part of release process and both
9.16 and 9.17 passed the test suite.
--
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 18. 6. 2021
On 18/06/2021 2:48 pm, Peter wrote:
> Even BIND9.16.18 will not run on windows 10 same error
I can't reproduce this error - I've just successfully upgraded from BIND
9.16.15 to BIND 9.16.18 on my Windows (2019) server.
Do you see a more detailed error in Computer Management > Windows Logs >
Ap
Even BIND9.16.18 will not run on windows 10 same error
On 18/06/2021 2:21 pm, Ondřej Surý wrote:
Hi Peter,
the Windows support in 9.17 has been discontinued (as discussed on this very
mailing list).
So, while technically the BIND 9.17.14/9.17.15 still includes the Windows
binaries, the
code h
Hi Peter,
the Windows support in 9.17 has been discontinued (as discussed on this very
mailing list).
So, while technically the BIND 9.17.14/9.17.15 still includes the Windows
binaries, the
code has been removed in the git repository, and the issue you are experiencing
will not
get a fix. If yo
Well I don't know about anyone else but BIND 9.17.14 did not want to
start in win 10 “windows could not start the ISC BIND service on local
computer Error 1067: the process terminated unexpectedly.”
___
Please visit https://lists.isc.org/mailman/listin
Hi again,
let me give you quick update again:
the development and support teams has found other use cases that would affect
both `w` and `W` letters in authoritative zones. The linked issue currently
talks just about the wildcards and we are going to update the issue shortly,
but I wanted to
Hi,
let me add more details to the issue.
# Who’s affected
Authoritative server operators operating zones with wildcard records (f.e.
*.example.com)
# What’s affected
Queries hitting the wildcard records with capital `W`
# How to test?
dig IN A W.example.com @127.0.0.1
You need to adjust t
Dear BIND users:
Yesterday, 16 June 2021, we released monthly maintenance snapshot releases of
our currently supported release branches of BIND.
Specifically, we released BIND 9.11.33, 9.16.17, and 9.17.14
There's no way to say this that isn't embarrassing, but only after the release
was an err
19 matches
Mail list logo
