IPv6 bug

[LawsHosting]

When you restore an account from another server, although you can specify a different IPv4 upon restore, you are unable to if it has an IPv6 too, hence it restores the old IPv6 into named... and therefore, the only way, is to delete them via the DNS Management page

Bug or is IPv6 still beta?

 

[DirectAdmin Support]

Hello,

Thanks for the report.
I've confirmed it as a bug, tested like this:

- created user with ipv6.com using IPv6 IP
- create backup of user
- delete user
- restore user, but "select IPv4 IP from list"

the swap doesn't cross A vs AAAA hence it gets a bungled up.

John

 

[DirectAdmin Support]

Fixed it up all, added entries here:
https://www.directadmin.com/features.php?id=1623

Point 3 also fixes restore from and old IPv6 to a new IPv6 (it will get rid of the old one), which is what your screenshot likely refers to.
I didn't test your screenshot in my original test, but the fix should apply to it too.

I'll upload the binaries to the pre-release section shortly.

John

 

[LawsHosting]

To add, I'm using a custom dns_a_ and dns_aaaa, and found that my webmail entry was outside the |*endif|, maybe this contributed to the mismatches of A vs AAAA (as seen in my screenshot)?

 

[DirectAdmin Support]

Ah, those were IPv6's in A records.. yes, that's possible.
Note that either way, you made me find a bug, if yours was different.

Now, a restore won't use the dns_a.conf or dns_aaaa.conf files at all, if the account is created from a backup.
But the others are still used, as they're often server specific settings.

John