Re: consolidating Reverse Zones

2021-10-21 Thread Mark Andrews
> On 21 Oct 2021, at 18:33, Edwardo Garcia wrote: > > Hai all, > > We have been given task of doing some migrations within new merger. > One of these is we have a number of reverse zones, a /19 in fact, they are > mostly GENERATE'd for regions with fixed gw and a few other local custom PTRs

Re: consolidating Reverse Zones

2021-10-21 Thread Grant Taylor via bind-users
On 10/21/21 1:33 AM, Edwardo Garcia wrote: Hai all, Hi, One of these is we have a number of reverse zones, a /19 in fact, they are mostly GENERATE'd  for regions with fixed gw and a few other local custom PTRs So 32 x /24s. Annoying, but not terrible to work with. In our examples I have

Pre-announcement of a BIND security issue scheduled for disclosure 27 October 2021

2021-10-21 Thread Everett B. Fulton
Hello, As part of our policy of pre-notification of upcoming security releases, we are writing to inform you that the October 2021 BIND maintenance releases that will be released on Wednesday, 27 October, will contain a patch for a security vulnerability affecting the BIND 9.11.x, 9.16.x and

Re: consolidating Reverse Zones

2021-10-21 Thread Tony Finch
Edwardo Garcia wrote: > > I guess bind can not consolidate like this and we have to put up with a > million /24 zone files ? I was thinking because we can do classless dele > with smaller than /24, it would work on bigger :) It is possible! The basic idea (very briefly) is: With classless reve

consolidating Reverse Zones

2021-10-21 Thread Edwardo Garcia
Hai all, We have been given task of doing some migrations within new merger. One of these is we have a number of reverse zones, a /19 in fact, they are mostly GENERATE'd for regions with fixed gw and a few other local custom PTRs I have played roughly with a fictitious in-addr.arpa (I play with