IPv6 address/prefix length mismatch
Summary
Used beef::10/64 as my IPv6 and wrote it to named.conf, and let named to load the configurations from the named.conf. The loading failed and named status was failed. However, when I used beef::0/64 , the loading was good, and named was started and running well.
BIND version used
9.18
Steps to reproduce
beef::10/64 as IPv6 and write it to named.conf
What is the current bug behavior?
/etc/named.conf:105: 'beef::10/64': address/prefix length mismatch '64.
`loading configuration: failure`
`exiting (due to fatal error)`
What is the expected correct behavior?
Relevant configuration files
named.conf
Relevant logs and/or screenshots
/etc/named.conf:105: 'beef::10/64': address/prefix length mismatch '64.
`loading configuration: failure`
`exiting (due to fatal error)`
Possible fixes
use beef::0/64. No any mismatch error. The loading was good.