I would suggest running your tests against a non-geobalanced and/or non-cdn enabled hostname (you can use the same resolvers, it doesn't matter here). Google m

I would suggest running your tests against a non-geobalanced and/or non-cdn enabled hostname (you can use the same resolvers, it doesn't matter here). Google most likely has a cache cluster within VM's core and their DNS send you there when you're resolving from VM's network (ipv4 case). When attempting to resolve over ipv6, you're not using VM's ip space but that of your tunnel provider. In this case, google's geo dns are likely to send you to another cluster closer to that provider.