"Chuck Swiger" wrote:
On Apr 11, 2018, at 3:32 PM, Rick Tillery wrote:
> I'll give those tools a try, but I don't understand how my client is
requesting an A record. It only has IPv6 networking. DNS64 should be
requesting an A record, but that the client should see is the
ger wrote:
> On Apr 11, 2018, at 3:09 PM, Rick Tillery wrote:
> > I appear to have my NAT64+DN64 IPv6 -> IPv4 network configured
> correctly, as I can access IPv4 only Internet sites, e.g. from my browser.
> But some tools don't seem to work the way I think they should.
>
I appear to have my NAT64+DN64 IPv6 -> IPv4 network configured correctly,
as I can access IPv4 only Internet sites, e.g. from my browser. But some
tools don't seem to work the way I think they should.
One example is nslookup. If do nslookup ipv4.google.com, I get:
$ nslookup ipv4.google.com
Ser
IPv6 network/DNS, right?
Rick
On Tue, Apr 3, 2018 at 8:36 AM, Mark Andrews wrote:
> Add exclude { ::/0; }; to the dns64 definition. It won’t prevent the
> lookup but will cause the returned to be ignored.
>
> --
> Mark Andrews
>
> > On 3 Apr 2018, at 23:14, Rick Ti
I am creating an IPv6-only subnet to test software for IPv6 compatibility.
We just need to check that the software can function correctly in an IPv6
network, so prefixed IPv4 addresses work the same as real IPv6 addresses in
this testing. We also don't actually need access to the IPv6 Internet,
ju
5 matches
Mail list logo
