DiG "unexpected source" with a Subnet-Router anycast address
François-Xavier Le Bail
fx.lebail at yahoo.com
Fri Sep 9 09:15:18 UTC 2011
--- On Wed, 9/7/11, Kevin Darcy <kcd at chrysler.com> wrote:
> Why are you trying to use the SRAA
> for DNS resolution? SRAA has a
> special meaning to network-infrastructure devices; I don't
> think it was
> ever intended for anycasting general network services. Just
> pick one of
> your global-unicast address, and anycast that instead.
We are testing a setup where the DNS querier don't know the GUA
but know the prefix (the GUA is EUI-64 generated, based on prefix).
The SRAA seems perfect for this use case.
Dig could have an option for "unexpected source" control based on the prefix to manage SRAA case.
[...]
> Note that RFC 4291 obsoletes RFC 3513 which obsoletes RFC
> 2373.
Right, but no changes about "Subnet-Router anycast address" in RFC 4291.
Francois-Xavier
> On 9/7/2011 10:48 AM, François-Xavier Le Bail wrote:
> > Hello,
> >
> > I send with DiG 9.7.3 a request to a router/DNS
> forwarder with the Subnet-Router anycast address of the
> router (SRAA, RFC 2373, § 2.6.1).
> >
> > The answer is :
> > reply from unexpected source:<GUA of the
> router>#53, expected<SRAA>#53
> >
> > Is there an option to relax the IPv6 address
> request/reply control for this use case ?
> >
> > Best regards,
> > François-Xavier Le Bail
More information about the bind-users
mailing list