User Profile
crustert
Newbie Caller
Joined 2 years ago
User Widgets
Contribuciones
Re: 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 areno 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 is172.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?19Visto3likes0ComentariosRe: Google blocking search
I think I figured out what the issue is after looking at multiple blacklisting sites, the issue looks to be happening due to there areno 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 is172.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.29Visto3likes0Comentarios