Chris Buxton wrote:
> Create RFC 1918 reverse zones for whatever parts of this address space
> you're using.
> Newer versions of BIND will do this automatically for you -- the zones
> are created without content. What version of BIND are you using?
Hm, anyone know which versions? The BIND 9.8 ARM has a section about
built-in empty zones, where it for example says "In particular, these
cover the reverse namespace for addresses from RFC 1918 and RFC 3330.",
then goes on to list several zones which are _not_ what I normally think
of when someone mention RFC 1918.
Also, from the source code of BIND 9.8.0, in the file bin/named/server.c -
there's a list of empty zones, but the RFC 1918 zones seem to be ifdef'ed
out:
#ifdef notyet
/* RFC 1918 */
{ "10.IN-ADDR.ARPA", ISC_TRUE },
{ "16.172.IN-ADDR.ARPA", ISC_TRUE },
{ "17.172.IN-ADDR.ARPA", ISC_TRUE },
{ "18.172.IN-ADDR.ARPA", ISC_TRUE },
{ "19.172.IN-ADDR.ARPA", ISC_TRUE },
{ "20.172.IN-ADDR.ARPA", ISC_TRUE },
{ "21.172.IN-ADDR.ARPA", ISC_TRUE },
{ "22.172.IN-ADDR.ARPA", ISC_TRUE },
{ "23.172.IN-ADDR.ARPA", ISC_TRUE },
{ "24.172.IN-ADDR.ARPA", ISC_TRUE },
{ "25.172.IN-ADDR.ARPA", ISC_TRUE },
{ "26.172.IN-ADDR.ARPA", ISC_TRUE },
{ "27.172.IN-ADDR.ARPA", ISC_TRUE },
{ "28.172.IN-ADDR.ARPA", ISC_TRUE },
{ "29.172.IN-ADDR.ARPA", ISC_TRUE },
{ "30.172.IN-ADDR.ARPA", ISC_TRUE },
{ "31.172.IN-ADDR.ARPA", ISC_TRUE },
{ "168.192.IN-ADDR.ARPA", ISC_TRUE },
#endif
Regards
Eivind Olsen
eiv...@aminor.no
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
