Google Maps Issue
It appears that Google has changed the domain structure for Google Maps. It was typically accessible at maps.google.com, but now that redirects to google.com/maps.
NextDNS is breaking many websites for me by incorrectly resolving maps.google.com. NextDNS was resolving it to 216.58.192.238 and maps.google.com would not load at all. Once I added "172.217.2.46 maps.google.com" to my hosts file, everything works great.
Why is NextDNS breaking Google Maps?
5 replies
-
Hello, I think Google moved maps.google.com to google.com/maps, maps.google.com redirects me too (without NextDNS).
I don’t really know where the issue is actually…
Also if NextDNS is braking some websites then try to not use lots of bloking lists, check also the logs and see if it’s needed (e.g. googleusercontent.com) domains are blocked.
I hope I helped someway ;)
-
YouTube is now doing something similar
With NextDNS
youtube.com -> 172.217.4.78
Per Google DIG
youtube.com -> 64.233.177.91
After setting this manual rewrite in NextDNS settings, youtube.com works great
-
Youtube (and many other services) are not hosted on 1 IP address. DNS is one of the mechanisms used to load balance users because you can give a different answers to multiple users. Besides that fact that it depends on WHERE the DNS resolver is that is doing the recursive lookup as it will, on many services, give you the IP address that is closest to you(r DNS resolver).
If you think NextDNS is "blocking" something why don't you create a new profile in NextDNS, configure the app on your device to use this profile and put all the blocking off (uncheck everything). If it works then it might be a blocklist or another configuration option causing this but I personally doubt it.
Content aside
- 3 yrs agoLast active
- 5Replies
- 274Views
-
4
Following