I have looked twice, there is no whitespace in the zone file.
If I change the conf file to present as a /16 it works fine, but we dont
have the /16 so we cant use it this way in production.
OK, we could, but that would be wrong because we are claiming dns of other
parts of /16 we have no rights to.
Wow, looks a right mess to be honest, might just have to leave it as is,
less aggravation.
Hard to understand why in 2021 almost 2022, we can't do something so simple
in dns
On Thu, Oct 21, 2021 at 9:49 PM Tony Finch wrote:
> Edwardo Garcia wrote:
> >
> > I guess bind can not consolidate like
> 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
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
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
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
6 matches
Mail list logo
