Re: ITS THE NUMBER OF CORES/THREADS

update on how to get bind to run with parameters for windows make folder in C:\ named make file called named.bat in the bat file add: sc start named -n 7 in services > ISC BIND recovery tab first failure select run a program check enable actions for stops with errors in run program browse

Re: ITS THE NUMBER OF CORES/THREADS

reproducer is helpful. Can you try if adding `-n 8` vs `-n 7` have the same effect? 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 23. 7. 2021, at 20:31, Peter via bind-users

Re: ITS THE NUMBER OF CORES/THREADS

Well I reported it and we see what happens my main bind is not in a virtual machine I guess I cound disbale Hyper-Threading as a workaround... ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds

ITS THE NUMBER OF CORES/THREADS

So after ALL that it was down to the number of cores/threads, anything more then 7 cores/threads and 9.16.19 WILL NOT RUN tested in avirtual PC. Man what A BUG ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from

Sorry

I have come to the conclusion that I am being punished! I have moved heaven and earth to get 9.16.19 to work and only seem to work on another old system Core™2 Duo that I installed win 7 activated it then upgrade to win10 only that system work with 9.16.19 on another system I remove NICs

New BIND 9.16.19 I think don't run with Intel VLANs

I have three PC's tested that all work fine on 9.16.15 or 9.17.12 with my Intel VLANs but 9.16.19 simply will not start. Is this a new limitation for BIND on windows now? or a change that causes it not to run if it detects VLANs with the intel APP?

Re: cmdns.dev.dns-oarc.net oddness with windows 10 and bind

Seems fine now they must of fixed the testing. ___ 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

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)

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

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. 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.

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)

n>named-checkconf C:\BIND\etc\named.conf:8: unknown option '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 discontinu

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? 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

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 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

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)

has been removed in the git repository, and the issue you are experiencing will not get a fix. If you want to keep running BIND 9 on Windows, you will have to downgrade to the lastest stable 9.16 release. Ondrej -- Ondřej Surý (He/Him) ond...@isc.org On 18. 6. 2021, at 14:46, Peter via bind

Re: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14

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

cmdns.dev.dns-oarc.net oddness with windows 10 and bind

So I redone my windows bind setup on a new system and this bug may never get fixed but I wanted to post the oddness of this bug. Bind on New PC as servers 127.0.0.1 for dns on that system cmdns.dev.dns-oarc.net reports fine except for IPv6 test OK I then have two PC's as clients to this DNS

Re: No more support for windows

Well its clearly not working so it needs to change just like DDNS is free but you can paid for a subscription thats easy to do or SSL is free for 90days but you have the option to pay easily for a year but that might not work for bind for windows so it needs to be a subscription to run it at

No more support for windows

On 04/06/2021 6:05 pm, John Thurston wrote: On 6/4/2021 8:48 AM, Peter via bind-users wrote: When people find out2024 is the year bind is no longer supported for windows people aregoing to be upset this all seems to be done quietly nothing posted on the the isc.org site about this just how

No more support for windows

When people find out2024 is the year bind is no longer supported for windows people aregoing to be upset this all seems to be done quietly nothing posted on the the isc.org site about this just how many people depend on bind for windows will be shocking.

Deprecating BIND 9.18+ on Windows (or making it community improved and supported

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 problem you want to edit a file no problem can't

Deprecating BIND 9.18+ on Windows (or making it community improved and supported

Maybe they could release a bind for windows ever year with limited support? But I guess bind will still work long after its not supported which is the only good thing. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe

Deprecating BIND 9.18+ on Windows (or making it community improved and supported

Well that sucks no more bind for windows...:( ___ 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

broken trust chain with my DNS setup

https://bridgemode.bounceme.net/DNS%20BIND%20setup2.txt %ProgramFiles%\ISC BIND 9\bin run CMD rndc-confgen -a folder managed-keys in ect file rndc.conf in etc include "C:\Program Files\ISC BIND 9\etc\rndc.key"; options { default-key "rndc-key"; default-server 127.0.0.1;

broken trust chain with my DNS setup

Hi hope someone can help here is my setup on Bind 9.17.10. https://bridgemode.bounceme.net/DNS%20BIND%20setup.html https://bridgemode.bounceme.net/DNS%20BIND%20setup2.txt When working what happens is: first lookup Lookup by