DNS64 & nslookup

[Mark Andrews]

Phones are a niche market. They don’t do DNSSEC. Some of them have a CLAT to handle IPv4 literals.

Also users are used to phones having restrictions on them which really shouldn’t be there and don’t get addressed even if you do complain so I wouldn’t take the lack of complaints as there are no problems. This is a industry wide issue. 
-- 
Mark Andrews

> On 13 Apr 2018, at 02:47, Lagerholm, Stephan <Stephan.Lagerholm1 at T-Mobile.com> wrote:
> 
> 
> 
> From: bind-users [mailto:bind-users-bounces at lists.isc.org] On Behalf Of Mark Boolootian
> Sent: Thursday, April 12, 2018 9:22 AM
> To: Mark Andrews <marka at isc.org>
> Cc: Bind Users <bind-users at lists.isc.org>
> Subject: Re: DNS64 & nslookup
> 
> 
> 
>> We've been running a DNS64/NAT64 without CLAT
>> net for a while without much trouble, but with a pretty
>> limited clientele.  The CLAT piece comes soon, and
>> access will expand.  If you really think this is asking
>> for trouble, I'd be interested in anything you can tell
>> me about said trouble.
> 
> Here at T-Mobile US we use DNS64/NAT64 setup extensively for all our Iphones (about 10 million give or take) without much trouble. And we have some 50 million Androids that are running IPv6 only with 464XLAT. 
> Every now and then we run into hostnames like:
> dig @ns1.discover.com. zinc-txn-notify.discovernetwork.com AAAA +norec
> That are totally busted and cause DNS64 to derail but we are just burning them down 1 by 1. I encourage you to join us in the IPv6-only world.  
> 
> 
>>> Thirdly, I wouldn’t rush to running IPv6-only.  It does have its advantages
>>> but they come with serious drawbacks.  At this stage IPv6-only is still
>>> niche only.
> 
> I would encourage you to rush into running IPv6 only. It is not niche only, DNS64 scales and works fine even without 464XLAT.  Break stuff and expose the brokenness is the only path forward. 
> 
> /Stephan