help wiht classless network and reverse lookups

Bill Dossett postmaster at bill.co.uk
Tue Mar 20 16:44:28 UTC 2001


I'm using version 8.something... should have mentioned that...
I've tried slash and dash, both produce the same results...
Any other ideas appreiciated... It sounds as though it should
work for my internal network, even if my ISP isn't set up
per RFC2317?

Thanks

Bill

Peter Anton wrote:

> on 3/20/01 9:18 PM, Bill Dossett at postmaster at bill.co.uk wrote:
> > named.conf contains
> >
> > zone "0-26.235.243.193.in-addr.arpa"{
> > type master;
> > file "193.243.235";
> > };
> >
> > 193.243.235 contains
> >
> > $ORIGIN 0-26.235.243.193.in-addr.arpa.
> > @    IN SOA     ns0.terrapin.co.uk.     postmaster.bill.co.uk. (....)
> > ...
> > @                       NS      ns0.terrapin.co.uk.
> > @                       NS      ns0.emtex.com.
> > 3                       IN      PTR     lucida.terrapin.co.uk.
>
> Here goes my first attempt at helping someone here... Second if you count
> the inadvertent empty message sent a moment ago, for which I now
> apologize...
>
> This may be way off base, as you implied you did not get error messages
> during the named startup in the logs.
> You also didn't mention which version you are using... But we're using
> 9.1.1, and I also had some trouble getting the classless delegation to work
> as well until...
>
> I realized that the recent versions do not support the range listed as
> 0-26.235.243.193.in-addr.arpa
> in the named.conf zone statement.
>
> Instead, try a slash:
>
> zone "0/26.235.243.193.in-addr.arpa"{
>             type master;
>             file "193.243.235";
>         };
>
> When I originally used the dash, I did get error messages during named
> startups and -HUP's, basically alerting me that the zone did not load
> properly.
>
> --
> Peter John Anton         Technical Manager, MicroPRINT
> Waltham, Mass., USA               781-890-7500
> peter at mprint.com



More information about the bind-users mailing list