We do what we can. But you'll note I said a) that it was happening to many other domains, and b) that my machines in that domain resolved fine from other connectivity. Cheers, - jra Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:

On Sat, Oct 26, 2013 at 12:27:25AM -0400, Jay Ashworth <jra@baylink.com> wrote a message of 31 lines which said:

...

I'm seeing, tonight, the inability to resolve DNS lookups for *some* domains, from my Sprint 4G phone. FB and Twitter are fine, and Currents can get to Android Central, frex, but panther.baylink.com, where my weather page resides, won't resolve,

No info but I note baylink.com has only two name servers and, much worse, they have the same IP address. So, any network glitch and the domain is unresolvable.

% check-soa -i baylink.com ns7.baylink.com. 66.221.0.238: OK: 2013073001 (124 ms) ns8.baylink.com. 66.221.0.238: OK: 2013073001 (125 ms)

-- Sent from my Android phone with K-9 Mail. Please excuse my brevity.