On Wed, Mar 31, 2010 at 02:45:09PM -0700, Dan Wing wrote:
> > On Mar 31, 2010, at 3:19 PM, Dan Wing wrote:
> >
> > > Any host that sends its AAAA queries over IPv4 would lose
> > > IPv6 connectivity.
> >
> > Isn't this a misdirection?
> >
> > I suspect it's more like: any (address family agnostic)
> > clients of a dual stacked nameserver will (non?)
> > deterministically lose IPv6 connectivity to DNS-determined
> > destinations.
> >
> > ie, even if I only send DNS over IPv6 to my recursive
> > nameserver, if it is dual stacked (often beyond my control),
> > and for this specific query it prefers IPv4, then I will not
> > get an answer for my AAAA under this proposal.
>
> It's likely cached by the ISP's nameserver, so it would work
> fine under Igor's proposal. And even if not cached, I would
> expect the content provider's authoritative DNS server to have
> whitelisted both IPv4 and IPv6 addresses of the ISP's
> nameservers.
>
> -d
i would hope that "big Brother" would quit trying to
be helpful. If I ask for AAAA, regardless of what
transport you receive the query on, please give me
what I ask for.
With forwarders, IMRs, and proxies josteling for position
between the stub and the authoritative server, its presumptious
and arrogant to presume that the transport the query was received
on is the same as the stub has.
DNS data has zero to do with the transport(s) queries are received
and responded to. Lets not conflate the two.
--bill
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
