Need help with your equipment?
nmb1983's profile

Tutor

 • 

4 Messages

Sunday, January 24th, 2016 12:52 AM

ATT U-Verse Blocking website IP

I've had this issue once before and ATT sent someone out to change out the router and the problem went away. Now month later i'm getting the same issues again getting the ERR-Connection Timed out just on my website. I do have access to any other site i punch in, just not my site. It seems to be a routing issue and as you can guess i'm about at my wits end with att U-verse...dragging thier dang feet with the issue. Any help to resolve this issue quickly would be freaking awesome.

Voyager

 • 

3 Messages

8 years ago

Not sure if problem is the same, but I have had problems the last several days with resolving hostnames for some of my websites. As best I can tell, ATT is having issues with their DNS nameservers. The nameservers provided to the NVG589 router (and  other ATT nameservers) do not resolve some hostnames. I see many "

no responses from nameserver '68.94.156.10'

" messages popping up in the router's Disgnostics/Logs. You can see if DNS lookup works/fails with a direct-to-server query using the nslookup command(in Windows PowerShell) :

-----------------
PS C:\Users\ken> nslookup www.google.com. 68.94.156.10
Server:  dns156r10.sbcglobal.net
Address:  68.94.156.10

Non-authoritative answer:
Name:    www.google.com
Addresses:  2607:f8b0:400d:c04::69
          173.194.205.106
          173.194.205.104
          173.194.205.103
          173.194.205.147
          173.194.205.99
          173.194.205.105

PS C:\Users\ken> nslookup www.romeoskyhawks.org. 68.94.156.10
Server:  dns156r10.sbcglobal.net
Address:  68.94.156.10

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to dns156r10.sbcglobal.net timed-out
PS C:\Users\ken> nslookup www.romeoskyhawks.org. 8.8.8.8
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
Name:    romeoskyhawks.org
Address:  208.64.38.87
Aliases:  www.romeoskyhawks.org

 

(ps. don't forget the dot after the hostname)

----------------

Note that the ATT 68.94.156.10 nameserver resolves the Google hostname, but fails to resolve the RomeoSkyhawks hostname. Changing the DNS server to Google's nameserver (8.8.8.8) resolves just fine...only the ATT servers seem to have the issue. As a workaround, it is possible to manually change the nameserver(s) that your PC's interface uses(pointing to non-ATT nameservers), and that's how I'm operating just fine now (with 8.8.8.8 and 8.8.4.4). I need a better solution since I can't fix the problem for all the other ATT Uverse customers trying to visit the website(s). Spent over an hour on the phone last night with ATT, visiting 3 levels of "help" getting everything from no understanding of DNS to "the nameserver address is not one of theirs" and they can't help. Searches in the inet uncovered many similar complaints over the last few years, with no resolutions other than bypassing the NVG router and providing your own router to distribute good nameservers to your PCs/Tablets/Smartphones.clients.

 

Expert

 • 

20.4K Messages

8 years ago

Ususally can get help from the web hosting company on non conneting websites, reason ATT blows you off.

 

Also if the website changed web hosting companies recently, new IP address needs to be repopulated into the DNS name resolvers.   Some big hosting companies will actually do it so their hosted websites show up and keep their customers happy. Smiley Surprised

 

Chris
__________________________________________________________

Please NO SD stretch-o-vision or 480 SD HD Channels
Need Help? PM ATT Uverse Care (all service problems)
ATT Customer Care(billing and all other problems)
Your Results May Vary, In My Humble Opinion
I Call It Like I See It, Simply a U-verse user, nothing more

Former Employee

 • 

422 Messages

8 years ago

@nmb1983

 

 

Just as @mibrnsurg stated, if there was a recent change to your websites hosting service and they are not one of the larger hosting providers, it may take some time for them to actually broadcast out that there information has been changed.

 

This doesnt only affect AT&T customers with the AT&T DNS servers, but also for other internet providers who have there own DNS servers.

 

 

In these situations you would need to speak with the website host to have them rectifiy the issue, as there wouldnt be anything AT&T or any other service provider can do.

Tutor

 • 

4 Messages

8 years ago

My domain is hosted through godaddy, but around thanksgiving we went with a place called Inventory Source to integrate our wholesalers inventory, but as far as i know the domain it's self is still hosted through godaddy. To throw a little more light on the situation...it started shortly after Thanksgiving, tried accessing my site ({Inappropriate content removed} it sat loading for maybe a minute or so and that's when i received the ERR Connection timed out so i contacted att  assured me they were on top of it. After about two weeks of waiting i contacted att again and they decided to send a Tech out to replace the router, Tech came out replaced the router and the problem was resolved. Now fast forward to Friday afternoon the issue presented it's self again, keep in mind as far as i know no changes were made to the DNS but i'm no tech nor do know much about all this (beyond my area of expertise) again got in touch with att and again assured me (the support specialist i spoke with) would personally see to it this problem is resolved quicker than the first go around (again to my knowledge) no changed were made. Now question being would it be to my benefit to contact Godaddy to see if maybe something changed that could have caused this to happen again?

Expert

 • 

20.4K Messages

8 years ago

@nmb1983  Will have to say Uverse had a big problem w/many godday websites a couple years ago, unable to connect to them.  This might just be a similar situation, but all had to complain to godaddy to get any action. Smiley Surprised

 

Edit:  Or at least your smaller web hosting company, probably running on godaddy.

 

Chris
__________________________________________________________

Please NO SD stretch-o-vision or 480 SD HD Channels
Need Help? PM ATT Uverse Care (all service problems)
ATT Customer Care(billing and all other problems)
Your Results May Vary, In My Humble Opinion
I Call It Like I See It, Simply a U-verse user, nothing more

Voyager

 • 

3 Messages

8 years ago

In my situation (hostnames not resolving on ATT Uverse DNS nameservers) its difficult to imagine that a local router swap by a tech could be helpful.  Direct DNS queries for name resolution (passing untouched from a PC to the suspect Uverse nameservers) demonstrate their failure to resolve the hostnames.
No DNS changes occurred witin the domain, and it was (still is) fully propagated within the Inet; all non-ATT nameservers tested resolve properly.  Curiously, ATT nameservers serving  the DSL environment resolve domain names okay too (dns.bna.bellsouth.net and dns.msy.bellsouth.net). At this point, I suspect that firewalls fronting the Uverse or hosting DNS server environment(s) are blocking the nameserver IP traffic. Since the website's IP is the same as the nameserver IP, and the website is fully accessible once the hostname is resolved (by other name servers),  I know that firewalls are not blocking normal IPV4 traffic. Will be discussing with hosting provider later tonight.

Former Employee

 • 

422 Messages

8 years ago

We still are having problems with GoDaddy, and they are unwilling to work with us.

 

So we have stop working on issues where hosting is by GoDaddy as its up to them to fix.

Tutor

 • 

4 Messages

8 years ago

My domain is still registered by Godaddy but inventory source is actually hosting the domain and website if that makes any sense

Former Employee

 • 

422 Messages

8 years ago

@nmb1983 right so the domain is what links your websites data, your service hosting your website source usually will have a seperate domain. For example if your with siteground.com for your hosting, there usually will be a subdomain off of your host as a backup that gets setup (ex. mydomainuser.siteground.com) and then your actual domain gets Parked onto the hosting servers and for them to route to the IP address of your server you need to set the nameservers of your domain to the nameservers provided by your hosting service.

 

 

So in this case this it how it works when going to yourdomain.com hosted by GoDaddy.

 

yourdomain.com (GoDaddy) --> ns1.siteground.com (Host provider nameserver) --> 111.111.111.111 (IP address where your source is stored on the server)

 

 

since the first step is going through GoDaddy and say there is an issue there, would be an issue GoDaddy would need to fix, if nothing wrong there it would then go to the Host provider which you can personally test usually if there is a subdomain setup on your host.

 

 

Voyager

 • 

3 Messages

8 years ago

Resolution to my problem...turned out to be a hosting environment firewall rule which was inadvertently dropping DNS traffic from AT&T Internet Services (“swbell.net”) devices in 151.164.109.* subnets. Since AT&T doesn’t seem to support reverse lookup for the addresses, we developed a rule to just pass all the IPs showing dropped traffic (which could include more than just nameservers). DNS started working immediately for the ATT-UVerse nameservers for multiple domains in that hosting environment. Will share specific IP ranges if desired...

Not finding what you're looking for?
New to AT&T Community?
New to the AT&T Community? Start by visiting the Community How-To.
New to the AT&T Community?
Visit the Community How-To.