Skip to main content
AT&T Community Forums
Announcements
The epic new Samsung Galaxy S21 5G is available for preorder now!
A

New Member

 • 

3 Messages

Sun, Feb 23, 2020 11:07 PM

Broken ATT DNS servers

Can someone fix the ATT DNS servers? My modem has this for configuration:

Subnet Mask 255.255.252.0

Default Gateway 172.1.84.1

Primary DNS 68.94.156.11

Secondary DNS 68.94.157.11

ping 68.94.156.11

PING 68.94.156.11 (68.94.156.11) 56(84) bytes of data.

64 bytes from 68.94.156.11: icmp_seq=1 ttl=56 time=41.6 ms

64 bytes from 68.94.156.11: icmp_seq=3 ttl=56 time=38.6 ms

64 bytes from 68.94.156.11: icmp_seq=4 ttl=56 time=39.0 ms

64 bytes from 68.94.156.11: icmp_seq=5 ttl=56 time=41.6 ms

64 bytes from 68.94.156.11: icmp_seq=10 ttl=56 time=40.1 ms

64 bytes from 68.94.156.11: icmp_seq=11 ttl=56 time=41.0 ms

64 bytes from 68.94.156.11: icmp_seq=12 ttl=56 time=203 ms

^C

--- 68.94.156.11 ping statistics ---

12 packets transmitted, 7 received, 41.6667% packet loss, time 11147ms

rtt min/avg/max/mdev = 38.579/63.616/203.418/57.084 ms

ping 68.94.157.11

PING 68.94.157.11 (68.94.157.11) 56(84) bytes of data.

64 bytes from 68.94.157.11: icmp_seq=1 ttl=56 time=50.0 ms

64 bytes from 68.94.157.11: icmp_seq=2 ttl=56 time=50.1 ms

64 bytes from 68.94.157.11: icmp_seq=4 ttl=56 time=47.9 ms

^C

--- 68.94.157.11 ping statistics ---

9 packets transmitted, 3 received, 66.6667% packet loss, time 8144ms

rtt min/avg/max/mdev = 47.913/49.339/50.117/1.009 ms

For reference, google DNS works fine:

ping 8.8.8.8

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

64 bytes from 8.8.8.8: icmp_seq=1 ttl=52 time=37.7 ms

64 bytes from 8.8.8.8: icmp_seq=2 ttl=52 time=37.9 ms

64 bytes from 8.8.8.8: icmp_seq=3 ttl=52 time=37.5 ms

64 bytes from 8.8.8.8: icmp_seq=4 ttl=52 time=41.2 ms

64 bytes from 8.8.8.8: icmp_seq=5 ttl=52 time=38.0 ms

64 bytes from 8.8.8.8: icmp_seq=6 ttl=52 time=38.3 ms

64 bytes from 8.8.8.8: icmp_seq=7 ttl=52 time=38.6 ms

64 bytes from 8.8.8.8: icmp_seq=8 ttl=52 time=38.9 ms

64 bytes from 8.8.8.8: icmp_seq=9 ttl=52 time=36.9 ms

64 bytes from 8.8.8.8: icmp_seq=10 ttl=52 time=37.6 ms

^C

--- 8.8.8.8 ping statistics ---

10 packets transmitted, 10 received, 0% packet loss, time 9014ms

rtt min/avg/max/mdev = 36.918/38.262/41.229/1.124 ms

In fact, every other DNS server I've tried works. Only ATT's are broken. When I use a different DNS server, everything works fine. No, my modem isn't broken and no it doesn't need to be rebooted or a factory reset.

Andy

Responses

Brand User
ATTHelp

Community Support

 • 

144.6K Messages

a year ago

We're here to help, @andyj713!

 

Could you let us know more about what you are experiencing, and how it is impacting your internet service? When it comes to the results viewed here, it only provides us a limited set of information on what the primary issue could be. Is thing giving you slow speeds, a high ping, or intermittent timeouts?

 

Let us know- we look forward to hearing back from you!

 

Donovan, AT&T Community Specialist

Still need help? Ask a question! Our 1.4 million members typically respond within 1 hour.

*I am an AT&T employee, and the postings on this site are my own and don't necessarily represent AT&T's position, strategies or opinions.

New Member

 • 

3 Messages

Obviously, packet loss means intermittent timeouts and slow name resolution which in turn results in high latency because of retransmissions. The information provided is sufficient for an experienced network technician to troubleshoot the problem. The problem is internal to ATT networks and servers, it does not appear to affect sites external to ATT. I don't have access to ATT equipment so I can't tell you why it's wrong, I can only see that it is wrong from the results. If you still have questions try searching the internet for some tutorial videos on how DNS works and the impact of packet loss.

Brand User
ATTHelp

Community Support

 • 

144.6K Messages

@andyj713

 

Our DNS servers have measures in place that might drop packets and cause pinging. We suggest switching to Google's DNS server for the time being. Let us know if you still have any issues.

 

Aminah, AT&T Community Specialist

Still need help? Ask a question! Our 1.4 million members typically respond within 1 hour.

*I am an AT&T employee, and the postings on this site are my own and don't necessarily represent AT&T's position, strategies or opinions.

New Member

 • 

3 Messages

Really. NOBODY would set up a DNS server that way intentionally. If I could set the DNS server addresses that the DHCP server in the ATT modem hands out I already would have. So what you are saying is that your systems and hardware are questionable at best, and I should consider alternatives. Thanks, but I am already working on that.

Mentor

 • 

59 Messages

@ATTHelp

Om March 25 2020 and now on March 28, 2020 the AT&T DNS cannot resolve the www.ssa.gov address and users cannot login to any social security sites.

The work around is by changing the DNS to the default google DNS IP 8.8.8.8 and 8.8.4.4 (IPv4), 2001:4860:4860::8888 and 2001:4860:4860::8844 (IPv6)

or going through a VPN server that uses a different DNS that the one used by AT&T. The failure seems related to the ATT IPv6 DNS. .

The AT&T DNS IPv4 68.94.156.1 and 68.94,157.1 and IPv6 2600:1700:d3f1:980::1 don't work and cannot resolve the Social Security addresses at all and users cannot connect .

Hmmm...can’t reach this page

Try this

Make sure you’ve got the right web address: http://www.ssa.gov

Search for "http://www.ssa.gov" on Bing

Refresh the page

Details

Report this issue

Privacy statement

(edited)

Mentor

 • 

59 Messages

I having problems with AT&T DNS too. To work around the problem I have to use some other public DNS, either open system or google DNS.
Problems started on 03/25/2020 and still happening on 04/01/2020.
It only worked for a few hours yesterday and then failed again.
The problem is quite simple, I cannot connect to any site of the social security administration. See results of nslookup ssa.gov below.
A technician came out yesterday and could not find the problem.
This is a specific problem of the ATT DNS, I'm located in zip 91932.

Microsoft Windows [Version 10.0.18363.752]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>nslookup ssa.gov
Server: homeportal
Address: 2600:1700:d3f1:980::1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to homeportal timed-out
C:\WINDOWS\system32>

Using OpenDNS works fine, but AT&T DNS is broken.

C:\WINDOWS\system32>nslookup ssa.gov
Server: resolver1.opendns.com
Address: 2620:119:35::35
Non-authoritative answer:
Name: ssa.gov
Addresses: 2001:1930:e03::aaaa
2001:1930:d07::aaaa
137.200.39.19
137.200.4.16

C:\WINDOWS\system32>

(edited)

New Member

 • 

2 Messages

5 months ago

BTW: You can access your AT&T modem by default webserver 192.168.1.254 then modify using access code printed on physical modem.

 

Have same problem. I can access via VPN , but not connected directly to AT&T modem. Having to rely on VPN, brings down the bandwidth and negates the use of AT&T. Many random sites are blocked because AT&T insists on locking down their DNS within the modem. You guys need to bring this to the top. Many customers and large businesses have complained about this and will be leaving AT&T.

 

I highly recommend, making the DNS standard as stated many times above or experience the result in future profit loss. 

It's not complicated unless AT&T doesn't understand the simple solution or are in denial to filter capture where customers are going on their paid service. 

 

If a AT&T technician does not understand this , please escalate to a higher level. 

Example; my DNS is hard locked to 

Primary DNS 68.94.156.1
Secondary DNS 68.94.157.1

 

Mentor

 • 

59 Messages

5 months ago

@Wilson2b,

 

The problem with AT&T DNS getting out of sync has been going on and off for a long time.

Eventually it syncs up and works, but may take several days.

A quick workaround waiting for the AT&T DNS to sync up, besides using VPN, is by changing the DNS to some public DNS like Google or Open DNS 

 

Google DNS:

  • For IPv4: 8.8.8.8 and/or 8.8.4.4.
  • For IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844.

 

OpenDNS:

For IPv4

208.67.222.222, 208.67.220.220

For IPv6

2620:0:ccc::2, 2620:0:ccd::2

 

https://support.opendns.com/hc/en-us/articles/227986667-Does-OpenDNS-Support-IPv6-

(edited)

New Member

 • 

2 Messages

5 months ago

@fg2001gfatID

 

Specifically, you mean change it on the the LAN router. Correct?

The DNS can not be changed on the AT&T modem.

 

On Ausus TR router, I did change the DNS primary and secondary as followed

1.1.1.1

&

8.8.8.8

 

Doesn't seem to help. Will try your suggestion

 

 

Mentor

 • 

59 Messages

4 months ago

 

 

Specifically, you mean change it on the the LAN router. Correct?

The DNS can not be changed on the AT&T modem.

 

On Ausus TR router, I did change the DNS primary and secondary as followed

1.1.1.1

&

8.8.8.8

 

@Wilson2b,

 

I have a AT&T Modem/Router combined (Pace 5268AC). I did not check if I can change it in that specific router.

If you cannot change it on the router, you can change it in the computer or computers if you have more than one. Ethernet and or Wi-Fi adapters, depending on which one you use

Changing the IPv4 may not be enough because they may use IPv6.

 

See setting samples below for windows 10 computer for IPv4 and IPv6 on the Ethernet adapter, the Wi-Fi adapter has the same type of setting:

 

 

 

 

(edited)

New Member

 • 

13 Messages

4 months ago

Why Does AT&T just not Fix the issues with their DNS Servers?   They are negatively impacting millions of customers who have the Uverse Service.  I have close to 35 devices that I would need to manually change the DNS on.   This issue is still going on and has not been addressed by AT&T.

New Member

 • 

4 Messages

2 months ago

I just figured out that the abysmal performance on our AT&T internet was their DNS servers. Pings literally dropped to 25% of what they were using the "get DNS from ISP setting". 

Traceroute now completes in seconds rather than minutes.

Oh, and Outlook is finally working at a reasonable rate.

I can't decide if this is incompetence in setting the configuration files or something more nefarious, but I'm going with Hanlon's razor.

https://en.wikipedia.org/wiki/Hanlon%27s_razor

My $0.02 is for anyone experiencing a DNS issue to set the primary and secondary to something beyond AT&T's DNS servers.

Get started...

Ask a new question