Google blocking search

crustert wrote:

I think I figured out what the issue is after looking at multiple blacklisting sites, the issue looks to be happening due to there are no reverse DNS records for the T-Mobile IPs, if a reverse DNS record does not exist for the IPs sites will blacklist the IP thinking it's a botnet.  For example, my home T-Mobile IP right this minute is 172.59.104.208, if I do a nslookup on this IP address:

C:\Users\XXXX>nslookup 172.59.104.208
Server:  XXXX
Address:  X.X.X.X

*** XXXX can't find 172.59.104.208: Non-existent domain

 

What should happen is this, which happens for an AT&T IP address:

C:\Users\XXXX> nslookup 107.77.199.13
Server:  XXXX
Address:  X.X.X.X

Name:    mobile-107-77-199-13.mobile.att.net <-----------------
Address:  107.77.199.13

 

So the issue is with T-Mobiles DNS servers, DNS reverse records are not working or are not setup for theirs IPs.

 

 

 

Has anyone from T-Mobile looked at my comment, I really think that is the issue?

It's possible that it is associated with the IP address.  T-Mobile Home Internet and cellular devices will change IP's as needed to balance traffic across the network.  

Hey there. That is a really weird error to be getting on a search. If I am understanding correctly, this error pops up right after typing a search before any search results come up. I would love to get some more information about the situation, so I can pass along the message for the really techy people to dig in and find out why. If you are comfortable sharing, I would love to know what you searched for, what time with time zone, and a screenshot of the error. If there is a hiccup with a set of our IP addresses and Google, then we want to tackle that asap. Thanks for sharing so we can figure it out!

This is happening to our household as well starting tonight. Only on the T Mobile home network.

Happening here too, NOLA IP address. Rebooted, got a new IP and issue still exists. 

I worked with chat support a little bit and they had me restart my router, we were able to get to google.com via Edge from a Windows machine but started getting the error from a phone again shortly after that.  I didn't have the time to stay on with them and keep trying stuff.  I sent them a link to this thread for reference.

I did confirm that we had a different IP address after the restart.

Happening to me in Florida as well. Only happens when at home and on my T-Mobile WiFi. Has anyone gotten an answer about this? I talked to a tech and he didn't even know this was happening.

Happening in Ohio also.  We get our IP addresses from Detroit it appears. This was before I rebooted but it keeps coming back.  I do not have same IP now.  All IP I have gotten and have this issue are in the 172.58.xxx.xxx range.

Happening to me in Michigan as well.

Update from T-Force for those interested:

"Our teams have confirmed they are aware of this happening, and they confirmed with Google that this isn't limited to T-Mobile Home Internet as it's happening with other ISP's as well. They noted that it isn't limited to a specific IP address, which explains why the troubleshooting we did didn't help, but as this is happening on Google's side of things, the fix for this will need to be processed on Google's side of things as well. 

They noted that some users reported that after performing a Cumulative update for Windows version 11 Version 22h2 for X64- based systems (KB5029263) and (KB5028948), all sites worked, so that's something you may be able to do on any Windows based systems that you're experiencing this on. Another thing I read was that some users reported being able to use Google though the web browser's incognito mode without consistently being asked, so that's another thing that may help for your other devices. 

I’m sorry I don’t have a more concrete answer on how or when this will be fixed, but I’m glad we were able to confirm that it’s not something to do with your Home Internet account and that both our teams and Google is aware of this happening!”