Priority of IPv4 and IPv6 addresses in Linux version?

Support
1

Hello,

I'm using Joplin Desktop 1.4.12 and CLI 1.4.9 on Linux Mint 20 LTS and having a problem on sync target host's IP address selection.

Sync. target is Nextcloud and the host has both IPv4 and IPv6 addresses.

Problem is that although the OS is configured to use IPv6 address first, Joplin apps access to IPv4 addredd. Because other Linux apps, such as ping, wget, SeaMonkey access to IPv6 address, OS configuration should be right. In addition, Android version of Joplin (1.3.13) also accesses to IPv6 address.

I prefer IPv6 to be used when available and as a workaround, I disabled the IPv4 address of the sync target host.

So, please tell me anything related to this problem.

Thanks in advance.

2

After a lot of investigation into Node.js, I found that the problem of IPv4 address used instead of IPv6 is Node's spec. For reference, here is a explanation of verbatim option of dns.lookup:

verbatim <boolean> When true, the callback receives IPv4 and IPv6 addresses in the order the DNS resolver returned them. When false, IPv4 addresses are placed before IPv6 addresses. Default: currently false (addresses are reordered) but this is expected to change in the not too distant future. New code should use { verbatim: true }.

I suppose Joplin doesn't call dns.lookup, but dns.lookup is called internally in Node when Joplin accesses to servers. In addition, there is no way to set/configure default value of dns.lookup's verbatim option.

The conclusion is that I (and Joplin) almost can do nothing to fix the problem except just waiting for the "not too distant future" of default value of verbatim to be true. (And it might not be very soon...)

PS. In my opinion, that Node's behaviour is (although it has been good when IPv6 was not very common) very outdated and doesn't match with RFC, and should be fixed soon... (Yes, this has nothing to do with Joplin.)