Only zones with wildcards affected on authoritative servers (Was: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14)

2021-06-18 Thread Ondřej Surý
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

Re: Only zones with wildcards affected on authoritative servers (Was: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14)

2021-06-18 Thread Ondřej Surý
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

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

2021-06-18 Thread Peter via bind-users
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

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)

2021-06-18 Thread Ondřej Surý
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

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)

2021-06-18 Thread Peter via bind-users
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

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)

2021-06-18 Thread Richard T.A. Neal
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

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)

2021-06-18 Thread Ondřej Surý
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

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)

2021-06-18 Thread Peter via bind-users
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: Limit actions on control channel?

2021-06-18 Thread Paul Kosinski via bind-users
It ought to be possible to write a front-end to listen on the standard control channel and only forward (properly-keyed) 'status' requests to the "real" port that BIND listens to. >From looking at the RNDC exchange via Wireshark however, you'd have to adapt >some of BIND's code that does the e

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)

2021-06-18 Thread Richard T.A. Neal
When you say “in Application logs show fine” – how far does named actually get (if at all)? For example whenever I (re)start the “ISC BIND” service on my Windows server I get *loads* of entries in the Application log, starting with these three: starting BIND 9.16.18 (Stable Release) running o

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)

2021-06-18 Thread Peter via bind-users
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

do I need to configure a Caching Server

2021-06-18 Thread techlists
I am building a home PHP hosting server for learning. I have a commercial connection to the Internet so no blocked ports and my ISP allows servers. I believe I only need a Primary Master Server. Is this the case? My question is, do I need to configure a Caching Server? In /etc/bind/named.co

Re: Only zones with wildcards affected on authoritative servers

2021-06-18 Thread John Thurston
On 6/17/2021 11:03 PM, Ondřej Surý wrote: # Are the ISC packages affected? The packages with the hotfix applied were pushed into the repository and are either already built or are building and will be available shortly The Ubuntu and Centos Copr packages are showing different version numbers

Re: Only zones with wildcards affected on authoritative servers

2021-06-18 Thread Ondřej Surý
John, yes, all ISC packages have fix to W problem either as a full release or a patch set. 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 18. 6. 2021, at 21:33, John T

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)

2021-06-18 Thread Richard T.A. Neal
The next Event Log entry on my system immediately after "using 1 UDP listener per interface" is: loading configuration from 'C:\BIND\etc\named.conf' (because that's my BIND installation folder obviously). If I intentionally make a typo in any of my config files (eg named.conf, named.conf.option

Origin of reverse lookup

2021-06-18 Thread techlists
Hi, I had my ISP configure a reverse lookup years ago. They say they no longer offer that service and there is no reverse lookup for my IP. I keep running into this old reverse lookup and do not know where it is coming from. When I run https://intodns.com/ it shows this reverse lookup and

Re: Origin of reverse lookup

2021-06-18 Thread Ralph Seichter
* techli...@phpcoderusa.com: > I had my ISP configure a reverse lookup years ago. They say they no > longer offer that service and there is no reverse lookup for my IP. And what exactly is "my IP"? One could hazard a guess based on your message's headers, but it would be easier if you told us. >