3 ms·
It should be noted, I forgot to include in the paste, that the address beginning with 62 (returned over IPv4) belongs to my ISP, not Google.
by aaronmdjones 12y ago
It should be noted, I forgot to include in the paste, that the address beginning with 62 (returned over IPv4) belongs to my ISP, not Google.
- opless 12y agoAlso on VM here. 'dig @8.8.8.8 +short A google.com' gives addresses in the 213.104.143.84-123 range. (actually appears in the 67-123 range) This isn't indicative of VM fiddling with DNS, just that there's some Google servers in VM's infrastructure. It's a common. In fact the addresses google spits out for google.com varies on your location, ISP etc. This is to redirect you to their closest endpoints, content delivery networks work in a similar way. Why does your IPV6 based query show differently? It's because of where your IPV6 tunnel is located. Looking from elsewhere in the uk I get 74.125.230.128-137,142