Cannot access 1.1.1.1

McGuywer

Executive Member
Joined
Jun 28, 2006
Messages
8,199
Reaction score
1,513
Location
Infinity and Beyond
Anyone else on rain with the same issue?

traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 10.791 ms 2.164 ms 2.072 ms
2 192.168.8.1 (192.168.8.1) 3.463 ms 2.982 ms 2.500 ms
3 * * *
4 ads-gi-01-eth14-22.rain.network (41.216.207.112) 22.072 ms 23.798 ms 28.699 ms
5 ads-igw-01-trk22-111.rain.network (41.216.207.80) 23.619 ms 29.644 ms 19.576 ms
6 tri-igw-01-trk101-100.rain.network (41.216.207.65) 23.195 ms 25.487 ms 16.758 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
 
Anyone else on rain with the same issue?

traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 10.791 ms 2.164 ms 2.072 ms
2 192.168.8.1 (192.168.8.1) 3.463 ms 2.982 ms 2.500 ms
3 * * *
4 ads-gi-01-eth14-22.rain.network (41.216.207.112) 22.072 ms 23.798 ms 28.699 ms
5 ads-igw-01-trk22-111.rain.network (41.216.207.80) 23.619 ms 29.644 ms 19.576 ms
6 tri-igw-01-trk101-100.rain.network (41.216.207.65) 23.195 ms 25.487 ms 16.758 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *

Perfectly normal.

Doesn’t mean you can’t access it, just means those hops have ICMP turned off.

Now if you couldn’t do “telnet 1.1.1.1 53” that would be unable to access it.
 
Here is the console:

Code:
Fetch event handler is recognized as no-op. No-op fetch handler may bring overhead during navigation. Consider removing the handler if possible.
 undefined
cannot-access-1-1-1-1.1329310/:1 Banner not shown: beforeinstallpromptevent.preventDefault() called. The page must call beforeinstallpromptevent.prompt() to show the banner.
/forum/posts/34159302/edit:1  Failed to load resource: the server responded with a status of 403 ()
core-compiled.js?_v=af63bd09:44 Error: 
defaultAjaxError @ core-compiled.js?_v=af63bd09:44
cannot-access-1-1-1-1.1329310/draft:1  Failed to load resource: the server responded with a status of 403 ()
 
There is no reason to be using curl to test 1.1.1.1 .Your telnet test suggests that port 53 is open , and in theory should respond to dns requests.However it could be that recursive queries have been blocked at the ISP.

BTW 1.1.1.1 hasnt been working on my cellc connection for a few years now.Either way just use 8.8.8.8 , 8.8.4.4. and call it a day.
 
Yes, looks like it.

I have had random GF issues, perhaps this is related to it.
I also have double NAT, will look at that in the new year.

Double NAT is pretty much always going to happen due to the nature of Rain's CGNAT configuration and no real way to get away from that.

Girlfriend issues I can't help with. :)
 
Double NAT is pretty much always going to happen due to the nature of Rain's CGNAT configuration and no real way to get away from that.

Girlfriend issues I can't help with. :)

cellc also uses cgnat and 1.1.1.1 not working as well.
 
Top
Sign up to the MyBroadband newsletter
X