invalid prefix

Michael Richardson mcr at sandelman.ca
Fri Mar 11 23:19:18 UTC 2022


I upgraded to 9.18 from 9.11 or something that was in debian nulleye.

Mar 11 18:14:27 tilapia named[9206]: /etc/bind/named.conf.options:40: invalid prefix, bits [64..71] must be zero

Alas, line 40 has multiple IPv6 prefixes on it:

40       dns64 2607:f0b0:f:0:ffff::/96 {
41          clients { 2607:f0b0:f::/56; 2a00:1098::/64; };
42          exclude { !2607:f0b0:f:3::184/128; !2607:f0b0:f:3:216:3eff:fe7c:d1f3/128; !2607:f0b0:f:2::30/128; };
42           mapped { !172.30.0.0/16; !10/8; !209.217.85.0/24; any; };
43        };

I feel a bit annoyed by this error, because it's kinda nice to be able to
just paste in stuff from ifconfig output, etc. and then say, yeah, let's do
the entire subnet.... but I understand that often it's a clue that someone is
clueless.

But, it would be great if the message told me which prefix was actually a
problem.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20220311/62527035/attachment.sig>


More information about the bind-users mailing list