On a system with only IPv6 access to the internet Virtualmin cannot be installed because the installation script download is timing out on the IPv6 address.
Also the installer itself is unable to download packages on IPv6 for the same reason, I guess.
By enabling IPv4 access as a secondary interface/gateway, things work, but only after attempts to connect over IPv6 time out.
I thought I’d point this out, perhaps the IPv6 config on the Virtualmin servers is not correct.
Hmmm…I’m not sure how that’d be a problem on our side. We don’t have IPv6 records for software.virtualmin.com, so your system should be using the IPv4 address (via an IPv6 to IPv4 gateway if your system doesn’t have IPv4).
We do have the ability to enable IPv6 for our mirrors, but it’s never come up as an issue, and I’m pretty sure I’ve tested downloads from it (I test on VMs at vultr and their cheapest VM only has IPv6 unless you pay more). But, I’ll experiment with that when I’m doing VM7 testing.
I don’t see how that’s possible. Our name servers have 0 AAAA records.
$ host -t aaaa software.virtualmin.com ns.virtualmin.com
Using domain server:
Name: ns.virtualmin.com
Address: 108.60.199.108#53
Aliases:
software.virtualmin.com has no AAAA record
I found out my mistake. I wasn’t in proper understanding of what DNS64 means.
I thought it was just a resolver that returns proper DNS records over IPv6 (but then it should’ve been named DNS128). But it turns out it is a resolver that synthesizes the IPv6 address of a DNS record if such address did not exist.
I was searching for the incorrect term (DNS64) and eventually using unwanted resolvers.