poor DNS service with AT&T Uverse

Bandit_Driver

Gold Member
Has anyone else been having problems with the board? In regards to slow page loads, or the site just not loading? I have ATT Uverse and was screwing around today and changed my DNS from ATT's to OPEN DNS and so far the problem has been fixed. Good performance now.

If anyone needs the DNS numbers here they are

208.67.222.222
208.67.220.220
 
AT&T hates African American Webmasters.

I'm kidding! :) Well at least I hope!

A lot of ISP's don't have a good working knowledge of DNS, hell, even I use OpenDNS here at the house!
 
You could try using the free public DNS service from Google. It works great, with the exception that some hotel internet that has a poorly configured DNS gateway won't work. So if you travel a lot to different hotels it might not be good for you.
 
AT&T hates African American Webmasters.

I'm kidding! :) Well at least I hope!

A lot of ISP's don't have a good working knowledge of DNS, hell, even I use OpenDNS here at the house!

:rotfl::rotfl:

I used to have it setup then I had to reset everything after a power outage and just forgot to add it back. It's night and day now most of the time. Every now and then I get a slow page load from JC but I am sure that is caused by something between my house and your servers.
 
This has been going on for over a year... I'm shocked that AT&T has not addressed the DNS problem by now.
 
A slow page load doesn't sound like a DNS issue. Typically a DNS issue would result in a Page Not Found. Have you tried the following when there is an issue.

C:\ping forums.jetcareers.com

If that fails then try ping 208.67.222.222

I would think that would fail too indicating a connectivy issue.
 
Some of the ISP's DNS doesn't get updated correctly or contain corrupted data. Cox's DNS servers were down for two weeks a few years ago until they got off their rump and recognized the problem.

It seems as if it's one of the least understood, most important parts of the intarwebs.
 
Oh, this is a DNS issue. I've talked to AT&T and told them exactly what the problem is, they just don't want to do anything about it since it does not effect a large segment of their users.

The work around as stated is use the open DNS server. I also run my own DNS server from the house of some things.
 
Back
Top