Skip to content

Instantly share code, notes, and snippets.

What would you like to do?
How to disable the very little-known AT&T setting that can appear to hijack your home DNS lookups and redirect to

How to disable the very little-known AT&T setting that can appear to hijack your home DNS lookups and redirect to


DNS queries on home network suddenly resolving hosts to


You will see SPORADIC mis-resolutions of EVERYTHING to that address if their crappy router happens to hear your PC's DHCP request - EVEN IF ANOTHER DHCP SERVER ON THE NETWORK assigns the ultimate address.

Do an IPCONFIG /ALL on the PC in question, and look carefully only at the DNS SERVER line....and note it is wrongfully THE ATT ROUTER ( in my case)!.  In almost every case, simply preforming a IPCONFIG /RENEW right there and again performing the /ALL, will then correctly show that YOUR DHCP SERVER'S ASSIGNED DNS SERVER is now listed.


Now, what REALLY took friggin digging including phone calls to finally find an engineer to let the cat out of the bag is why the "" address?  Where is that coming from?

So my bet is you also don't know that by default AT&T has taken upon itself to forcibly inject it's own DNS server (as the router) with the latest round of firmware and unless you TAKE ACTION TO OPT-OUT, will intercept your DNS queries via new changes in router firmware pushing out the router as DNS server.

AT&T's VERY HIDDEN "helper" redirection for DNS that YOU MUST OPT-OUT of is named "DNS Error Assist" which causes this unwanted behavior.


Here is how to disable AT&T's "DNS Error Assist" service on your account. 

NOTE, this does NOT fix the recent router firmware issues that also re-enabled IPv6 without notifications that is also allowing THEIR ROUTER to continue to hand-out DNS even when you set a single IP pool range for DHCP with a non-existent reservation (which should in effect kill all DHCP on their router from handing out ANYTHING). This appears to be a firmware issue with no known current workarounds other than to take precautionary measures to ensure your DHCP replies first.

  1. Navigate to and in the upper-right LOGIN
  3. Click "Communication preferences".
  4. Click "Privacy Settings".
  5. Click "DNS Error Assist " and FRIGGIN CLICK OPT-OUT!!  This is what is redirecting (via the router) your DNS queries ACTIVELY TO THEIR SERVER ( is an AT&T address via Rackspace).

(OPTIONAL):  While there, you may also choose to click "External Marketing & Analytics Reports", "Relevant Advertising", and "Enhanced Relevant Advertising" and also OPT-OUT of all of those that they also DO NOT TELL YOU THAT YOU HAVE ENABLED ON YOUR ACCOUNT.

Note this is actually a per-use back-end server setting and as you will see the DNS setting says it can take up to 24hrs whereas the more "typical" privacy crap of the advertising etc. will tell you up to a week to be effective, further supporting that the "DNS error assist" is an infrastructure-based setting being pushed to your router that they not only know they have recently put into place, but have the ability to disable.

Copy link

@nathan-alden-sr The note about IPv6 saved me today from a lot of head-banging and hair pulling. Thank you.

Copy link

The URL (and subsequent updates) provided here used to work for me, but when I visit the cmpportal page now I get a message that states:
"We couldn't locate an account for this ID. Select Register Now to create an AT&T Access ID. Link all of your accounts and enjoy the ease of using a single ID and password."

However, I'm logged in with my AT&T Access ID.

I found their (new?) DNS Error Assist page for my account at:


The problem I'm having is that even though I've disabled DNS Error Assist, it still redirects browsers to a page instead of failing as expected.

When I try to visit a non-existing domain (


Copy link

Not sure if this is new, but under

my profile > privacy choices

there was a checkbox to allow ATT to share or sell your personal info. I opted out before but it was checked again when I just went back and looked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment