[Slackbuilds-users] ftp server not accessible

[B. Watson]

On Sat, 22 Feb 2025, Noel Butler via SlackBuilds-users wrote:

> 
> On 21/02/2025 19:40, Marco Moock wrote:
>
>       Am 21.02.2025 um 19:38:50 Uhr schrieb Noel Butler via SlackBuilds-users:
>
>             I don't know why Marco is not getting in on ipv4 as you said,
> 
>
>       The machine I used is intentionally only connected to IPv6 (with
>       NAT64/DNS64).
> 
> 
> Ahhh OK, in doing so you know and accept the risks, unfortunately like the one you are experiencing now.

Actually... if I understand how NAT64 and DNS64 work, he should be
able to connect to the IPv4 address if there's no AAAA record at all.

See https://en.wikipedia.org/wiki/IPv6_transition_mechanism#DNS64

DNS64 gives a 'synthetic' IPv6 address for a real IPv4 one, and NAT64
allows an IPv6-only host to connect to it.

AFAICT, the problem is caused by us having an AAAA record, but not
really listening on the IPv6 address.

His machine doesn't think it needs to use DNS64/NAT64 because it
sees there's a real AAAA record, so it tries to connect to the real
IPv6 address, which gives 'connection refused'. If we got rid of the
AAAA record entirely, DNS64 and NAT64 would be used instead.

At least that's what it looks like based on the 5-minute crash course
I just gave myself on DNS64 and NAT64.

Marco, is that correct?