address/prefix length mismatch

[Elias Pereira]

Hello Greg,

Why doesn't bind work with networks/subnets in the conventional way?

If the private subnet is 10.60.0.0/23, then it means that the address range
is 10.60.0.1 to 10.60.1.254.

How do I configure this ACL in named.conf.local so that it takes the whole
range?

On Wed, Aug 24, 2022 at 9:31 AM Anand Buddhdev <anandb at ripe.net> wrote:

> On 24/08/2022 14:16, Elias Pereira wrote:
>
> Hi Elias,
>
> > Oh, sorry... :D
> >
> > here it is
> >
> > # cat named.conf.local
> > # ACL das redes internas
> > # Ultima modificação: 24/08/2022
> >
> > acl "internal" {
> > 10.60.0.1/23;
>
> This is the issue. The address part of the prefix should be the lowest
> address in that prefix. If you change this to 10.60.0.0/23, it will be
> fine. The same goes for all the other prefixes in your list. Change the
> 1's to 0's.
>
> > 10.10.1.1/24;
> > 10.10.2.1/25;
> > 10.10.3.1/25;
> > 10.10.4.1/25;
> > 10.10.5.1/25;
> > 10.51.0.1/23;
> > 10.10.6.1/25;
> > 10.10.7.1/26;
> > 172.20.0.1/26;
> > 10.50.0.1/23;
> > 10.40.0.1/22;
> > 10.56.0.1/22;
> > };
>


-- 
Elias Pereira
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20220824/1a06e790/attachment-0001.htm>