On Fri, May 17, 2019 at 2:13 PM Stuart Henderson wrote:
> On 2019/05/16 23:37, Rachel Roch wrote:
> > > RFC3513 says this:
> > >
> > > o An anycast address must not be used as the source address of
> > > an IPv6 packet.
> > >
> > > o An anycast address must not be assigned to an IPv6 host,
To chime in here, how I have always implemented Anycast DNS
is by creating additional Loopback adapters in the OS, and then
using BGP or OSPF to distribute said Loopback IPs into a routing
table.
Each DNS server participating in Anycast would have the same
IPv4 and IPv6 address configured on that
On 2019/05/16 23:37, Rachel Roch wrote:
>
>
> > RFC3513 says this:
> >
> > o An anycast address must not be used as the source address of
> > an IPv6 packet.
> >
> > o An anycast address must not be assigned to an IPv6 host, that
> > is, it may be assigned to an IPv6 router only.
> >
> > And
> RFC3513 says this:
>
> o An anycast address must not be used as the source address of
> an IPv6 packet.
>
> o An anycast address must not be assigned to an IPv6 host, that
> is, it may be assigned to an IPv6 router only.
>
> And to help ensure this, the kernel denies binding to an address
(moving from misc to tech)
On 2019-05-11, Rachel Roch wrote:
> I'm still learning IPv6 intricacies, so forgive me if this is a silly
> question.
>
> When I have interfaces set in the standard manner, e.g.:
>
> inet6 2001:DB8:beef::1 128
> up
>
> NSD and Unbound will bind to that address without
I'm still learning IPv6 intricacies, so forgive me if this is a silly question.
When I have interfaces set in the standard manner, e.g.:
inet6 2001:DB8:beef::1 128
up
NSD and Unbound will bind to that address without problem.
However if I add the anycast flag:
inet6 2001:DB8:beef::1 128
6 matches
Mail list logo
