Seems 2.53 has a DNS bug, With Ipv6 prefered it its only checking for AAAA record and not A. This results in any tracker with no AAAA (IPv6) failing with "Host not found".

Now if it was set to IPv6 only this could be acceptable, but IPv6 prefered should query both, and simply prefer IPv6 when it works.

This is still a bug in 2.55.

Steps to reproduce.

1: Set Ipv6 Preferred.
2: Let or Force Tixati to query a IPv4 only tracker. It will show "Host not found". sniffing traffic show Tixati only querying for an AAAA record only.

What should happen: Tixati in IPv6 prefered or IPv4 prefered should query for both AAAA and A, and prefer one or other but if one is missing use what ever is available.

using ipv6 preferred few years now, never had this issues, nor do i have it now

any example of not working tracker?

Any, literally any tracker that has no AAAA/IPv6 will not resolve, Running wireshark shows only an AAAA queries no matter the tracker. And trackers show "Host Not found (49410)"

This is still an issue in 2.56.

Note this is on Windows, Specifically 2016 Server (i.e. Windows 10 Server)

This is still an issue on 2.58

Still happens in 2.62