<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Oops...<br><blockquote type="cite"><div style="PADDING-LEFT: 10px; PADDING-RIGHT: 10px; WORD-WRAP: break-word; PADDING-TOP: 15px; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space" id="MailContainerBody" leftmargin="0" topmargin="0" canvastabstop="true" name="Compose message area"><div><blockquote type="cite"><div style="PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: 15px" id="MailContainerBody" name="Compose message area" leftmargin="0" topmargin="0" canvastabstop="true"><div><font face="Calibri">DS-Lite client needs to be implemented as a
protocol on the CPE. NAT64 has a big catch in that it assumes your PC (or
smart mobile host for that matter) is <em>not</em> on dual-stack, i.e. an
IPv6-only host, which is a challenge. NAT64 also needs reworking the DNS
infrastructure.</font></div>
<div><font face="Calibri"></font></div></div></blockquote>
<div><br></div>This is not necessarily true, but, if your PC is dual stack and
wants to receive literal A records,</div>
<div>it should need NAT64 and shouldn't be talking to a NAT64 nameserver.</div>
<div><br></div></div></blockquote>That should read:</div><div><br></div><div>...it does not need NAT64 and shouldn't be talking to a NAT64 nameserver.</div><div><br><blockquote type="cite"><div style="PADDING-LEFT: 10px; PADDING-RIGHT: 10px; WORD-WRAP: break-word; PADDING-TOP: 15px; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space" id="MailContainerBody" leftmargin="0" topmargin="0" canvastabstop="true" name="Compose message area">
<div>It is true that if you are running a NAT64 resolver, the resolver will not
respond with legitimate</div>
<div>A records for IPv4-only hosts and will instead provide mapped AAAA
records.</div>
<div><br></div>
<div>This is pretty trivial to work around using one of two techniques:</div>
<div><br></div>
<div><span style="WHITE-SPACE: pre" class="Apple-tab-span"></span>+<span style="WHITE-SPACE: pre" class="Apple-tab-span"> </span>Use different resolvers
for NAT64 and non-NAT64 clients.</div>
<div><span style="WHITE-SPACE: pre" class="Apple-tab-span"></span>+<span style="WHITE-SPACE: pre" class="Apple-tab-span"> </span>Provide different views
for NAT64 vs. non-NAT64 clients.</div>
<div><br></div>
<div>Partial NAT64 implementations (hosts that are dual stack for a subset of
the IPv4 internet</div>
<div>but don't have global IPv4 connectivity) are a different problem. This
configuration should</div>
<div>generally be avoided anyway.</div>
<div><br></div>
<div>Owen</div>
<div><br></div></div>
</blockquote></div><br></body></html>