Re: Only zones with wildcards affected on authoritative servers

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: Only zones with wildcards affected on authoritative servers

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 (Was: Important: A significant flaw is present in June BIND releases 9.16.17 and 9.17.14)

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

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)

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