Get superfast AT&T Fiber internet
youdontknowme's profile

6 Messages

Thursday, February 29th, 2024 3:30 AM

Closed

No Longer Able to Use 3rd-Party DNS Servers After 12-Hour Outage ???

TL;DR: after a recent 12-hour outage, my wired AND wireless devices can no longer use AdGuard DNS servers to resolve DNS. I had to go back to using AT&T's DNS to "get things working" again.

I have Fiber 300, BGW320-500 gateway, version 4.25.4. I had a 12-hour outage the other day (red blinking light, the gateway GUI still detected the SFP module but it "wasn't seeing any light" so to speak, Phone Support was unable to resolve [but confirmed no neighborhood/area outage], so they dispatched a tech). But a few hours before the tech was supposed to arrive, everything miraculously started working again, so I promptly cancelled the tech (didn't want to be charged a fee if he couldn't find anything wrong while on-site).

OK so I use AdGuard DNS on my wired equipment and wireless devices. Or I did. I can't now after that outage. DNS resolutions all fail now UNLESS I use AT&T's DNS servers.

How things were configured:

On wired equipment, I just used 94.140.14.14/94.140.15.15 simple DNS, (no secure DNS etc). After the outage, DNS resolutions would just downright fail. I tried 8.8.8.8 and 1.1.1.1 and same thing. I then set it to populate the DNS server from DHCP (just the modem), and that works.

On my wireless devices (all Android), I used Android's Private DNS feature pointed to dns.adguard-dns.com. But after the outage, the devices would "connect without Internet." On each device, I first tried using just Private DNS Default, but same thing. So completely disabling Private DNS, the devices all resolved DNS just fine. The caveat here is Private DNS to AdGuard still works on other Wi-Fi networks, and for those devices that are also cellular, AdGuard Private DNS still works over 4/5G as well.

So I'm about at my witts' end here. What else can I try to get this to "just work" again? Has there been some coincidental update to gateways that purposely now prevents customers from using their own DNS servers now (which if so then I think that's ridiculous)? This isn't making any sense anymore.

Or (this just hit me before posting this) should I just jump to "Plan Z" and put the gateway in "dumb mode" and put my own Wi-Fi router behind it? I didn't go this route at first because I wanted to give the gateway a chance (plus I don't do anything fancy like port-forwarding, run any servers, anything like that)

Thank you!

ACE - Expert

 • 

35K Messages

2 months ago

While I've heard people claim similar experiences to yours, I've not seen it first hand.  You can put your own router behind the Gateway, setting up IP Passthrough mode in the Gateway for your router.  However, If UDP 53 traffic is being blocked without your own router, I see no reason why it would not continue to be blocked with your own router, as the UDP 53 traffic (or TCP 853 in the case of your Android Private DNS) will still have to go through the Gateway and the AT&T network.  You could, however, implement DoH in your router, tunnelling the DNS traffic in a way that it could not be detected by the AT&T network gear. 

Community Support

 • 

231.3K Messages

2 months ago

Hi @youdontknowme, we understand that you're facing difficulties using third-party servers, and would like to help. Let's get the assistance you require.

 

We'd recommend you to try this below mentioned basic troubleshooting steps.

 

You can also try optimizing your internet connection, this will help with re-syncing.

 

Restart your Wi-Fi gateway

  • Unplug the power cord from the back of your gateway or modem. If you have: 
    • An internal battery backup, remove it
    • DSL, unplug the phone cord from your modem or gateway
  • Wait 20 seconds.
  • Put the internal battery back in if you have one. 
  • Plug the power cord back in. If you have DSL service, reconnect the phone cord.
  • Wait for the gateway or modem to restart and your Broadband light to turn solid green. This can take up to 10 minutes.

 

Also, you can try resetting your Wi-Fi gateway.

If the issue persists, we'd recommend you to add an additional router using IP Passthrough. For more information please visit our article about configuring IP Passthrough and DMZplus.

Let us know if this helps.

 

Thank you for contacting AT&T Community and Forums,

Ancy, AT&T Community Specialist.

 

6 Messages

2 months ago

Hi! Thank you for the responses! Apologies for the scatterbrained-sounding original post. I was letting this issue get to me for too long and too late last night.

This morning I did install the AdGuard app onto one of my phones, and onto one of my Windows PCs. And, I mean, they do work. I might just accept that as an adequate workaround for now and get it installed on my other stuff. (But I'm just one of those weirdos who don't like using extra software to fix non-software issues LOL)

Now don't get me wrong, I have nothing directly against using AT&T's DNS specifically. I just want to use The Web "without all the (Edited per community guidelines)," if you know what I mean <wink>, so is why I use an ad-and-tracker-blocking DNS. And it doesn't "have" to be AdGuard's DNS (but others didn't work either) -- I've just been using AdGuard happily for years so I'm just used to it.

I could get a wifi router and "bridge" the modem and go that "route" (no pun intended)... I can get a decent new-old-stock Wireless-AC router for super cheap at my work and just try it out. (Wireless-AC should be sufficient for Fiber 300 -- I don't need the Latest & Greatest)

Yeah, spinning up a PiHole came to mind as well.

Oh yeah, I failed to mention I hadn't called the hotline about this yet. I wasn't sure if they'd be able to help with a weird issue like this, or just give me the runaround, etc etc? I could try "when I feel like it."

Thanks again!

(edited)

Community Support

 • 

231.3K Messages

2 months ago

Hi @youdontknowme,


We hear you and would like to help, as you're facing issue using third-party servers. Let's guide you in the right direction.

The Community Forums are a public support option where other users, and AT&T, will try and assist with high level support needs.   This means we won’t be able to look into account specific concerns.  To get the help you need for your unique issue, please review our Contact Us page:https://www.att.com/support/contact-us/, and choose the best option to reach out to us.  You can call, chat, or reach out via social media, and we can review your specific issue and provide you support.  If you feel your issue isn’t account specific, and can be answered generally, please let us know, and we’ll be happy to help.

 

Thank you for visiting AT&T Community Forums!

Jennifer, AT&T Community Specialist. 

 

6 Messages

1 month ago

Hi again!

Just an update, and new issue appeared (or better-manifested itself???), which I know I'll have to bug the hotline on this one. DNS resolutions to the router's gateway's DNS (which then go to sbcglobal's DNS) are now timing-out randomly on all equipment/devices. With and without the newly-installed AdGuard app, protection enabled or not, doesn't matter. At least DNS queries to standard DNS aren't getting blatantly blocked, but there's noticeable degredation now (but so much that I had to crowbar some entries in my Windows PC's hosts file to at least continue to function without pulling my hair out on some things)

I kinda still wanna try "bridging" the gateway and trying my own wi-fi router. I should acquire the wifi router tonight. (If that solves everything then I'll just keep that solution, hoping something else doesn't keep getting worse, which seems to be the experience lately...) Otherwise yes fun times calling the hotline (I hate calling hotlines... <facepalm>)

I'm just sharing my experience "just in case this helps others" (or if anybody even cares LOL) but if I just need to close this, I can too.

(edited)

6 Messages

1 month ago

Heyo!

I finally "bridged" the gateway and popped the new WifiAC behind it about an hour ago. I specified AdGuard's DNS on the new router and left devices fully DHCP. Surprisingly, smooth sailing so far, with confirmed ad- and [bad word]- blocking. Knock on wood.

And trying nslookups on my wired Windows PC, and digs on my wireless Android tablet, no more random time-outs, all queries were snappy, some as little as 18 ms. And queries to known ad and tracker domains returned zeroes. Rock on!

If this setup continues to behave for a few more days, then I'll come back and mark this as Solution Found.

Fluff info: -------------

I bugged a coworker of mine today, who also has AT&T Fiber, about my situation, he finally stopped me and told me, "Dude, just bridge the gateway and get your own router---that seems to solve many peoples' problems." LOL!

Oh and I did call the hotline this afternoon, and the [somewhat snippy?] woman was blaming a severed intercontinental fiber line in the Red Sea??? Seriously? LOL? (I mean, I suppose such an event could be plausible with the current conflicts happening in that area, but I live in The Middle of Nowhere America, my traffic shouldn't all be going through the Red Sea LOL!!!), so I politely ended the call.

Community Support

 • 

231.3K Messages

1 month ago

Thanks for writing back to us.

It's great news that things are running smoothly now! If you continue to have problems in the future, please do not hesitate to contact us. We are more than happy to help!

Thank you.
David, AT&T Community Specialist.

ACE - Professor

 • 

5.4K Messages

1 month ago

You can’t bridge past the gateway.  What you would have to do although not specifically stated is to use IP passthrough, so for completeness you should state for all this is the step you’ve taken.  
Also, while you may not care for Att’s default DNS , I and many others use it fine with no issues or concerns.  You want to use your own router, fine, but this is a one off as far as I’m concerned.  Good luck.  

6 Messages

1 month ago

No go. The DNS timeouts came back, and are even worse now. Even undoing the "bridge" IP passthrough 😉 and going back to regular AT&T DNS. Something somewhere sees to be fudging with DNS. I tried packet loss tests and each one passed 100% so it's not that. I'm becoming a very unsettled camper here. I'll be duking this out with the hotline for now on...

(edited)

6 Messages

1 month ago

Hi again!

Apologies for sounding angry at the end of my last post. I didn't mean it like, "I'm done with Forums," but more like, "I'll try to work with the hotline on this particular issue from that point."

And none of my calls to the hotline yielded any true solutions. They either didn't fully understand my issue, or were adamant that they are not blocking third-party DNS servers. And when I agreed they send a tech to my home, he acted inconvenienced and indifferent the whole time, left a mess in my "home offic" room and was condescending... I finally tactfully ended the visit.

And yet the underlying DNS timeout issue has not been resolved yet.

Aside from cancelling my service out of pure frustration and going back to cable (which is reported to still be ridiculously unreliable in my neighborhood, but at least they [used to] gladly let you use whatever DNS you darn well pleased), I finally gave up fighting this issue. I otherwise still enjoy my Fiber service.

I just ended up fully-registering the AdGuard app on my PCs and devices. Now, not that I'm expecting anyone to resolve this next statement: I STILL encounter some DNS timeouts on the PCs, but not as often---but the wireless devices do not luckily. I might need to weak the AdGuard app on my PCs.

So . . . still unresolved (and I'm still very disappointed that AT&T [at least in my area] is, beyond my reasonable doubt, blocking third-party DNS servers). So my current AdGuard solution [mostly] works. I just had to throw a bit of money at the problem (paying for a lifetime AdGuard license).

Whenever I feel like taking on a cute littly nerdy weekend project, I might try getting a Pi Hole going.

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.