This doesn't appear to be an IPv6-specific issue. In principle named should
also be capable of listening on all of 127/8, but I can't find any
configuration syntax that will do more than listen on 127.0.0.1. I can ping
127.0.0.2 (and so on) but even explicitly adding listen-on 127.0.0.2 won't
c
I have reloaded the configuration as well as restarted the bind9. The
simpliest workaround I see - bind IPv6 explicitly to the interface using
command "ip address add 2001:db8::1 dev eth0" and then I am able to use
2001:db8::1 for the named. But I would like to take advantage of using
AnyIP.
Just a quick question because I ran into this problem before... is it
possible that named was started before the ip was added?
On Sun, Mar 12, 2023 at 12:55 PM Serg via bind-users
wrote:
>
> Hello, I am trying to bind named listener to an IPv6 from prefix which
> is assigned to a system via AnyIP
Hello, I am trying to bind named listener to an IPv6 from prefix which
is assigned to a system via AnyIP kernel feature - basically, it is done
by the following command: sudo ip -6 route add local 2001:db8::/32 dev lo.
To be able to use IPv6 from AnyIP prefix the following sysctl must be
appli
4 matches
Mail list logo
