If they didn't want people using other DNS, and were willing to fuck with ip addresses they don't own to accomplish that, they'd be blackholing google's and opendns's public caching nameservers too. From what I've read, the routers use it on some internal interface. They were blocking 1.1.1.1 on some firmwares long before cloudflare's dns service started. No way 1.1.1.1 is completing in under 1ms haha Pings to 8.8.8.8 from the diagnostics page take about 23 ms. The times on the pings make it look like its hitting a loopback address instead.
One interesting thing is that if I go to the gateway management page, and use their diagnostic tools, I'm able to ping / traceroute the address - but I can't from any devices connected to the gatewayĦ4 bytes from 1.1.1.1: seq=0 ttl=64 time=0.568 msĦ4 bytes from 1.1.1.1: seq=1 ttl=64 time=0.156 msĦ4 bytes from 1.1.1.1: seq=2 ttl=64 time=0.164 msĦ4 bytes from 1.1.1.1: seq=3 ttl=64 time=0.144 msĤ packets transmitted, 4 packets received, 0% packet loss I have ATT U-verse internet service and use their Arris BGW210-700 gateway It worked for a day or so and then stopped. 8.8.8.8 works, but their IPv6 doesn't, so I guess this was a bad test.Įdit2: Learned about nslookup, but it does not seem to work with either Google or CloudFlare's DNS. We also need to confirm IPV6 works outside AT&T's network.Įdit: Just tried Google's DNS. It’s not as easy to get cool IPv6 addresses however, we’ve picked an address that only uses digits.įor me up in Canada, ping 1.1.1.1 works.
0 kommentar(er)
