As of now connectivity-check.ubuntu.com has still no AAAA record and... it causes no IPv6 problem on Ubuntu 20.04. I doubt it ever did.
"ping www.google.com" and "getent ahosts www.google.com" show that the system prefers IPv6 anyway. As expected, only changing /etc/gai.conf makes "ping www.google.com" and "getent ahosts www.google.com" prefer IPv4. Nothing else does. I also tried to change the connectivity uri to http://fedoraproject.org/static/hotspot.txt (which has AAAA) and it made no difference whatsoever anywhere compared to connectivity- check.ubuntu.com > As a result, the IPv6 default routes will be heavily deprioritised (ie: having 20000 added to the metric) My default IPv6 route had a 20100 metric in every single combination I tried. Using fedoraproject.org made no difference. Note I have a single wired interface, no wifi. AFAIK IPv6 route metrics are only compared to other IPv6 routes, not to IPv4 routes. It's not like each packet has a choice between the two. PS: see #1880258 for another, unrelated connectivity-check.ubuntu.com issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815036 Title: uri defined for connectivity check does not have IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
