DNS resolving issues with AT&T Customer Resolvers

[mark at viviotech.net (Mark Keymer)]

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 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,

-- 

Mark Keymer