[190561] in North American Network Operators' Group
Re: DNS resolving issues with AT&T Customer Resolvers
daemon@ATHENA.MIT.EDU (Mark Keymer)
Fri Jul 8 16:51:54 2016
X-Original-To: nanog@nanog.org
To: nanog@nanog.org
From: Mark Keymer <mark@viviotech.net>
Date: Fri, 8 Jul 2016 13:52:04 -0700
In-Reply-To: <768031b8-2606-b004-2f3a-8dbc36e4d478@viviotech.net>
Errors-To: nanog-bounces@nanog.org
The specific DNS server that are not resolve for my client are.
Primary DNS 68.94.156.9
Secondary DNS 68.94.157.9
If any AT&T people out there that can look into this. Thank you.
Sincerely,
Mark Keymer
On 7/8/2016 12:36 PM, Mark Keymer wrote:
> Hi all,
>
> I have a client bridgecatalog.com and it seems like customers with
> AT&T are unable to resolve his Domain. Maybe I am just overlooking
> something here but it seems like all should be working. Looking at
> outside tool things look ok too.
> http://dnscheck.pingdom.com/?domain=bridgecatalog.com
>
> (except the SOA hostmaster@solarek.com e-mailing issues I see now)
>
> Other domains seem to work fine. So it isn't just everything is down.
> One of the end-users I was working with currently has an ip of
> 99.7.225.25. Power cycling the modem did not change thing. I also
> flushed DNS. If I change to google's open resolvers things work fine.
> But not with default resolvers to client.
>
> Anyone at AT&T that could check that the resolver's your clients are
> using are able to resolve. (Home / SMB connections, etc)
>
> I am not sure the best way to go about trying to look into this issue
> if other have suggestion I would also appreciate it.
>
> Sincerely,
>
