Re: [93attendees] IETF Meeting NAT64 network

[Tore Anderson <[e-mail]>]

* Diego Garcia del Rio

> I tried to revert to ietf-nat64 when the wifi went doesn't and
> unfortunately encountered two issues. One was that for whatever
> reason, the DNS resolution for one of our company's vpn endpoint was
> being answered as an IPv4 record. Couldn't figure out the logo why to
> be honest.

Hi Diego,

DNS64 does not filter out IPv4 addresses; IN A records are returned
normally. The synthetic IPv6 IN AAAA responses are returned *in
addition* to the upstream IN A records (assuming the application
queries for both). So what you describe is actually expected behaviour.

FWIW I spent most of my time on ietf-nat64 as well, using Linux with
464XLAT. It was working very nicely, and I think better than plain
"ietf", except for some connectivity issues I had on Tuesday
(periodically losing the ability to communicate with the default router
and beyond with unicast frames). That was not a NAT64 problem though,
but an IPv6-only problem that applied to ietf-v6only as well -
as I understand it, the wireless infrastructure assumed that clients
without a (non-169.254.0.0/16) IPv4 address weren't at all interested in
having network connectivity...

Tore