Comment 5 for bug 734781

That was my reasoning too, since people are *still* trying to work out IPv6. And you can still get IPv6 answers via IPv4 nameservers too, which depends on the IPv4 nameservers being set up correctly with AAA records of course.

Note that glibc also has a maximum of *3* 'nameserver' entries in resolv.conf, so if we really had both IPv4 VPN & normal and IPv6 VPN and normal nameservers, we'd be one over the limit. The only way to fix this is to use a local caching nameserver.

glibc queries the nameservers in the order they are listed in resolv.conf, so if the IPv4 servers don't know the address of the IPv6 machine it should fail and glib will query the IPv6 server. The apps themselves are the things that request AAA records (IPv6) instead of the A records and they are the ones that decide what to do with the records that actually get returned too. So unless the app is badly coded, is there a real difference which nameservers are first? Is ordering necessary to work around bad servers?