To:
David Terrell <dbt@meat.net>
Cc:
Robert Elz <kre@munnari.OZ.AU>, ngtrans@sunroof.eng.sun.com, ipng@sunroof.eng.sun.com, dnsop@cafax.se, namedroppers@ops.ietf.org
From:
Johan Ihren <johani@autonomica.se>
Date:
15 Aug 2001 12:30:37 +0200
In-Reply-To:
David Terrell's message of "Wed, 15 Aug 2001 03:21:35 -0700"
Sender:
owner-dnsop@cafax.se
User-Agent:
Gnus/5.070095 (Pterodactyl Gnus v0.95) Emacs/20.3
Subject:
Re: (ngtrans) Joint DNSEXT & NGTRANS summary
David Terrell <dbt@meat.net> writes: > > But there's no way to get everyone to have it - which means that > > administrators will always have to add AAAA records so those people > > can find their web server, mail server, .... And if AAAA records > > have to exist, and resolvers will be looking for them (because no > > way are all servers going to start supplying A6 all at once, even > > with a fairly broad concept of the time quantum) then there's no > > point adding A6 records at all - they'd be just one more thing that > > has to be maintained (excess duplicate data). > > There's no reason why it can't be a gradual upgrade. Authoritative > servers for zones with A6 can do AAAA synthesis at query time just > as easily as the local non-stub resolver can. It becomes a server-side > indirection mechanism, which is available to A6-grokking caches. This is *wrong*. An authoritative, non-recursive server with only A6 fragments around can not synthesise the AAAA since that would require it to query for missing fragments. Johan Ihren