Very weird Geo Location issue

[iansays]

The Eero is set for WAN DHCP (of course) and it inherits its DNS servers from Sonic's gateway (50.0.1.1 and 50.0.2.2). "Bypassing" the Eero, whether by turning off wifi and using cell data on my phone, or connecting my laptop to my phone's hotspot, or some other method of NOT using my home IP to access the internet, results in access to the sites I can't access otherwise.

On my laptop (connected to the Eero), I am using Google's and Cloudflare's DNS servers, hard coded into my NIC's TCP/IP v4 properties. 8.8.8.8 and 1.1.1.1.

On any other connected device (my cell phone, my wife's iPhone, an iPad, an Android tablet, etc..) it would be using Sonic's DNS servers as passed on from the Eero's DHCP settings.

All devices can NOT access the 'blocked' sites. So, seems any local DNS settings are not affecting access.

>For what its worth I can access those sites without issue via Sonic fiber.

Not surprising, since I suspect it's my single IP (again, "my IP" is the IP of my whole building) that is being blocked by some Google resource.

Tracert, which is identical (aside from the ms of each hop) no matter if I hard code DNS servers or let my NIC be assigned Sonic DNS servers:

C:\Users\ian>tracert viewfromthewing.com

Tracing route to viewfromthewing.com [35.227.46.114]
over a maximum of 30 hops:

1 7 ms 5 ms 5 ms 192.168.4.1
2 7 ms 9 ms 7 ms lo0.bng1.snjsca02.sonic.net [157.131.132.138]
3 11 ms 14 ms 13 ms 192-184-185-18.static.sonic.net [192.184.185.18]
4 8 ms 9 ms 18 ms ae2.cr2.snjsca02.sonic.net [192.184.184.250]
5 23 ms 21 ms 26 ms ae1.cr3.lsatca11.sonic.net [192.184.184.241]
6 11 ms 14 ms 16 ms ae2.cr4.lsatca11.sonic.net [157.131.242.233]
7 17 ms 16 ms 13 ms ae4.cr1.lsatca11.sonic.net [135.180.179.193]
8 221 ms 216 ms 202 ms ae0.cr4.colaca01.sonic.net [157.131.243.25]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 9 ms 10 ms 9 ms 100.ae1.nrd1.equinix-sj.sonic.net [75.101.33.185]
17 11 ms 11 ms 9 ms google.159.ae1.nrd1.equinix-sj.sonic.net [209.148.113.38]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.


Ian

[js9erfan]

The Eero is set for WAN DHCP (of course) and it inherits its DNS servers from Sonic's gateway (50.0.1.1 and 50.0.2.2). "Bypassing" the Eero, whether by turning off wifi and using cell data on my phone, or connecting my laptop to my phone's hotspot, or some other method of NOT using my home IP to access the internet, results in access to the sites I can't access otherwise.

Yeah, I meant physically bypassing the eero with a laptop by connecting the laptop to the ethernet port where the eero is currently connected. Your laptop may even pull a different wan IP from Sonic. I don't use eeros but they appear to have an ad/domain blocking feature and thought that could be part of it. But it looks like that's not the case assuming 192.168.4.1 is your eero.

Unless you're on cg-nat I assume you have a different wan IP than your neighbors. Have you checked with any of them to confirm? Eventually your Sonic IP will change so hopefully that will resolve your issue without having to use a vpn, etc.

Best of luck

[iansays]

Just to close this loop for anyone who was interested.

Whatever Google was doing to map my IP to Iran has now been fixed. Or, rather, I assume the record linking my IP to Iran timed out or expired.

No explanation of course. it just started working again (to access those sites and apps I could not access before).

Thanks to anyone who read or commented. Sorry I don't have more info. Just a glitch in the Matrix, I guess.

Ian