Forum Discussion
DNS Blocking on T-Mobile Gateway, Gateway Refuses to Accept Connection
Have been having issues lately and did some deep trouble-shooting today.
All the usual trouble shooting, restart reboot gate way, reboot router, reset gateway, reset router, unplug devices, etc…
Found the issue was the gateway kept reporting it was connected but the router which is wired directly to the gateway said there was no connection.
I normally use an alternative dns provider for everything, as the ISP provided dns is slow and insecure subject to dns jacking.
As soon as I switch the router to use the ISP Provided dns from the gateway it connected perfectly, devices that were manually configured with the alternative dns on their interfaces still couldn’t connect though.
Switching these devices to the ISP Provided dns solved their issue as well.
Only thing that is working with the alternative dns without issue is the Secure DNS protocol which appears to be immune to what ever is going on with the t-mobile ISP.
I don’t know if this is a bug or a feature in t-mobile’s book or this is due to their main internet gateway provider somehow getting jacked.
djb14336 wrote:
Basicslly, they need to fix the dual-stack problem.
Trying to force everything across an IPv6 only network just ramps up the complexity... don't think they were quite ready for primetime with this.
IPv6? did you detect ipv6? I tried to detect it and didn’t.
I’ve been on the phone with them a couple times to complain about the dual-stack issue. I’m on the phone again right now and I’ve been subjected to 30 minutes of silent hold so far. I’m about to call up Verizon and see about their fixed wireless home internet service.
Basicslly, they need to fix the dual-stack problem.
Trying to force everything across an IPv6 only network just ramps up the complexity... don't think they were quite ready for primetime with this.
Yep, I was trying to think of an innocent answer to this problem.
Just maybe they have t-mobile using a private dns for name translation for servers needed to connect on the t-mobile network and since other dns providers don’t have the ability to translate these names into an ip address the connection fails.
If so, who ever set this up failed to realize how badly they had broken everyone’s internet connection.
I actually noticed this myself. My Apple TV was using the Cloudflare DNS 1.1.1.1 and it’s been blocked, my dad’s Chromecast uses Google’s own 8.8.4.4 and 8.8.8.8 DNS servers and it can’t connect to ANYTHING and I can’t change the DNS on the Chromecast. I also had nothing but issues from my Desktop (Windows and Linux), Laptop (Linux), and Tablet (Linux). Until I changed off the Cloudflare DNS to Automatic DNS.
Good News everyone! secure dns is coming to windows 10, it is available on beta builds now.
https://lifehacker.com/how-to-turn-on-dns-over-https-for-all-apps-in-windows-1-1843544589
