--- On Mon, 9/12/11, Kevin Darcy wrote:
> You should either a) pursue with your network hardware
> vendor why its device is responding to a query to the SRAA
> with a different source address, thus breaking the rules of
> DNS resolution, or b) select a working resolver address in
> the Global Uni
On 9/9/2011 5:15 AM, François-Xavier Le Bail wrote:
--- On Wed, 9/7/11, Kevin Darcy 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
--- On Wed, 9/7/11, Kevin Darcy 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, an
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.
There was an old Internet-Dra
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: #53, expected #53
Is there an option to relax the IPv6 address request/reply control for this use
case
5 matches
Mail list logo
