[189475] in North American Network Operators' Group
Re: Public DNS64
daemon@ATHENA.MIT.EDU (Mark Andrews)
Sun May 29 21:40:00 2016
X-Original-To: nanog@nanog.org
To: Tim Durack <tdurack@gmail.com>
From: Mark Andrews <marka@isc.org>
In-reply-to: Your message of "Sun, 29 May 2016 21:07:31 -0400."
<CAE_ug16_y+Ww8B3vkh-V4RNgGJyGcT9GH65z7uYpf_-XuR_ReA@mail.gmail.com>
Date: Mon, 30 May 2016 11:39:50 +1000
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
DNS64 is a bad solution. It breaks DNSSEC. The proported benefits of
DNS64 over other ways of providing IPv4 over IPv6 don't actually exist.
DS-Lite or one of the MAP encapsulation will actually be better in the
long run.
I say this as someone who has written a DNS64 implementation.
Mark
In message <CAE_ug16_y+Ww8B3vkh-V4RNgGJyGcT9GH65z7uYpf_-XuR_ReA@mail.gmail.com>
, Tim Durack writes:
> For the record:
>
> Tim,
>
> I'm not on the NANOG lists and I don't see how I can respond to this thread:
>
> https://mailman.nanog.org/pipermail/nanog/2014-August/069267.html
>
> but I figured I'd let you know that:
>
> https://developers.google.com/speed/public-dns/docs/dns64
>
> is now available for testing. Perhaps it will be some use.
>
> Regards,
> -Erik
>
> On Fri, Aug 15, 2014 at 2:29 PM, Tim Durack <tdurack@gmail.com> wrote:
>
> > Anyone know of a reliable public DNS64 service?
> >
> > Would be cool if Google added a Public DNS64 service, then I could point
> > the NAT64 prefix at appropriately placed boxes in my network.
> >
> > Why? Other people are better than me at running DNS resolvers :-)
> >
> > --
> > Tim:>
> >
>
>
>
> --
> Tim:>
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
