DNS resolving issues with AT&T Customer Resolvers

Hiawatha Demby hdemby at email.unc.edu
Fri Jul 8 19:55:29 UTC 2016


C:\Users>nslookup bridgecatalog.com
Server:  UnKnown
Address:  192.168.0.1

DNS request timed out.
     timeout was 2 seconds.
DNS request timed out.
     timeout was 2 seconds.
DNS request timed out.
     timeout was 2 seconds.
DNS request timed out.
     timeout was 2 seconds.
*** Request to UnKnown timed-out

C:\Users>nslookup bridgecatalog.com 8.8.8.8
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

DNS request timed out.
     timeout was 2 seconds.
DNS request timed out.
     timeout was 2 seconds.
DNS request timed out.
     timeout was 2 seconds.
DNS request timed out.
     timeout was 2 seconds.
*** Request to google-public-dns-a.google.com timed-out

C:\Users>nslookup bridgecatalog.com 68.94.156.15
Server:  dns156r15.sbcglobal.net
Address:  68.94.156.15

DNS request timed out.
     timeout was 2 seconds.
DNS request timed out.
     timeout was 2 seconds.
DNS request timed out.
     timeout was 2 seconds.
DNS request timed out.
     timeout was 2 seconds.
*** Request to dns156r15.sbcglobal.net timed-out

Looks like the AT&T server are unavailable and the host is unresolvable 
on my end.

On 7/8/2016 3: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. 
> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fdnscheck.pingdom.com%2f%3fdomain%3dbridgecatalog.com&data=01%7c01%7chdemby%40email.unc.edu%7ca1a111c28862421e835f08d3a7672759%7c58b3d54f16c942d3af081fcabd095666%7c1&sdata=OhVtZs8EqOGddhZh26uvcnMLBBZ5CiUTdeX9FXy5twk%3d
>
> (except the SOA hostmaster at 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,
>




More information about the NANOG mailing list