3 Messages
broken DNS on UVerse static IP
The addresses in our static netblock are listed by AT&T with "uvs.hstntx.sbcglobal.net" as their parent domain, but this domain no longer exists.
As a result, our reverse DNS records no longer forward-resolve. This causes our hosts to be rejected by servers.
A quick look at other AT&T addresses reveals the problem also affects some other customers, including those in "lightspeed.rcsntx.sbcglobal.net".
Note, only a technician or engineer in the AT&T Internet backbone engineering group can address the problem, because it is entirely a function of AT&T corporate global infrastructural master server configuration, and can only be addressed by repairing the misconfiguration.
ATTHelp
Community Support
•
232.1K Messages
17 days ago
Hi @douzzer2! Thank you for reaching out to us! We hear you, and are happy to guide you.
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 contacting AT&T Community Forums!
Nate, AT&T Community Specialist.
0
0
douzzer2
3 Messages
17 days ago
I'm not asking a question nor am I asking for support. I'm providing information. PTR records without forward A records are being published for AT&T network address space. Two of the forward zones at issue are uvs.hstntx.sbcglobal.net and lightspeed.rcsntx.sbcglobal.net. There may be others. This is a serious misconfiguration and it is not specific to my account, or apparently even to my metro region.
To fix the problem, action must be taken by higher-level AT&T technicians/engineers. This is an infrastructure configuration problem.
0
0
JefferMC
ACE - Expert
•
35.5K Messages
16 days ago
If you'd like, you could say "Alexa, " ("Siri" or "Hey Google" would also work just as well) and report your problem. Speak slowly and clearly. Or mumble quickly. You don't even have to have the appropriate device for that wake-up keyword.
It will have nearly the same result as posting here, other than someone else who has noticed the symptom can be informed that you have also noticed the symptom. AT&T will take no useful notice of your post, unless those other users pipe up. And without corroborating information from other users, I'm not going to fight that fight to attempt to get it noticed.
0
0