Leaderboard

I can confirm that when using the one Air-account device for which I have adblocking configured, I can switch back and forth between OpenVPN -> Air server and wireguard -> Air server and watch the results of running dig on "ad-delivery.net", one of the domains listed by Air as blocked, and see the result toggle between 0.0.0.0 and three IPv4 addresses. I'm getting DNS adblocking via openVPN but not via wireguard. Experiments with newspaper apps confirm. Adblocking works with OpenVPN but not with wireguard. Experiments used iOS 15.1 and the ISC Dig app, the WireGuard app, and the OpenVPN Connect app, and Firefox Mobile. I verified at ipleak.net that the wireguard experiment is using Air DNS and not my router's DNS setup. iOS is IPv6 capable, but my router setup is not, and my Air wireguard configs specify IPv4 transport but IPv[46] both on exit from the Air server. In ipleak.net, both IPv4 and IPv6 addresses show for the wireguard server (labeled Chamaeleon), but the single DNS server IP shown matches the wireguard server IPv4 address (again labeled Chameleon). I have not modified the wireguard config from Air's config generator (other than config name). The DNS field in the config is indeed the .1 address of the Addresses subnet, but the DNS server listed by dig is a different 10.X.Y.Z address, one that is not in the Addresses subnet. Doesn't seem shocking to me, but maybe staff will read and infer something that I cannot.