Reverse Zone CIDR

Jonathan Del Campo jdc at mikrosimage.eu
Wed May 25 10:35:13 UTC 2016


Thanks Anand,

I don't have any errors logs to answer Tony, but just the "dig +short -x
192.168.223.42" doesn't return anything.

So if I have to create two /24 reverse zones for my case, I will, but I was
hopping a smarter solution.

Should I have to create two reverses zones definition in my dhcpd.conf
file, like this ?

subnet 192.168.222.0 netmask 255.255.254.0 {
        # pool d'adresses IP dynamiques
        pool {
                range 192.168.222.20 192.168.222.253;
                range 192.168.223.20 192.168.223.250;
        }

        ddns-domainname                 "domain.int";
        option routers                  192.168.223.254; # default gateway
        option subnet-mask              255.255.254.0;
        option broadcast-address        192.168.223.255;
        next-server                     192.168.200.19;
        filename                        "undionly.kpxe";
        allow bootp;
        allow booting;

        # Zone reverse
        zone 222.168.192.in-addr.arpa. {
                primary 192.168.200.1;
                key mikros.int;
        }

        zone 223.168.192.in-addr.arpa. {
                primary 192.168.200.1;
                key mikros.int;
        }
}


Thanks,

On Wed, May 25, 2016 at 11:52 AM, Anand Buddhdev <anandb at ripe.net> wrote:

> Hi Jonathan,
>
> If it's a /23, may I suggest creating two reverse zones, for each of the
> /24s in that prefix? It's much simpler.
>
> RFC 2317-style delegation, while possible for a /23, was designed for
> IPv4 prefixes smaller than a /24.
>
> Regards,
>
> Anand Buddhdev
> RIPE NCC
>
> On 25/05/16 11:37, Jonathan Del Campo wrote:
> > Hello,
> >
> > We are trying to create a zone for a /23 subnet (192.168.222.0/23), but
> we
> > can't get the reverse zone working.
> >
> > There is our config :
> >
> > */etc/named/domain.int.zonefile :*
> >
> > zone "0/23.222.168.192.in-addr.arpa" IN {
> >     type master;
> >     file "dynamic/0-23.222.168.192.in-addr.arpa";
> > };
> >
> >
> >
> > */var/named/dynamic/0-23.222.168.192.in-addr.arpa :*
> > $ORIGIN .
> > $TTL 3600       ; 1 hour
> > 0/23.222.168.192.in-addr.arpa IN SOA    dns1.domain.int.
> sysadmin.domain.eu.
> > (
> >                                 2013021143 ; serial
> >                                 1200       ; refresh (20 minutes)
> >                                 3600       ; retry (1 hour)
> >                                 1209600    ; expire (2 weeks)
> >                                 3600       ; minimum (1 hour)
> >                                 )
> >                         NS      DNS1.domain.int.
> > $ORIGIN 0/23.222.168.192.in-addr.arpa.
> > $TTL 86400      ; 1 day
> > 102                       PTR     vegeta.domain.int.
> > ...
> >
> >
> > I don't know if the naming convention is correct ( 0-23 vs 0/23 ) ?
> >
> > Can you please help ?
> >
> >
> >
> > _______________________________________________
> > Please visit https://lists.isc.org/mailman/listinfo/bind-users to
> unsubscribe from this list
> >
> > bind-users mailing list
> > bind-users at lists.isc.org
> > https://lists.isc.org/mailman/listinfo/bind-users
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20160525/3af47c2d/attachment.html>


More information about the bind-users mailing list