<html><head></head><body>We do what we can.<br>
<br>
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. <br>
<br>
Cheers, <br>
- jra<br><br><div class="gmail_quote">Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On Sat, Oct 26, 2013 at 12:27:25AM -0400,<br />Jay Ashworth <jra@baylink.com> wrote <br />a message of 31 lines which said:<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">I'm seeing, tonight, the inability to resolve DNS lookups for *some* domains,<br />from my Sprint 4G phone. FB and Twitter are fine, and Currents can get to <br />Android Central, frex, but <a href="http://panther.baylink.com">panther.baylink.com</a>, where my weather page resides,<br />won't resolve, </blockquote><br />No info but I note <a href="http://baylink.com">baylink.com</a> has only two name servers and, much<br />worse, they have the same IP address. So, any network glitch and the<br />domain is unresolvable.<br /><br />% check-soa -i <a href="http://baylink.com">baylink.com</a> <br /><a href="http://ns7.baylink.com">ns7.baylink.com</a>.<br /> <a href="http://66.221.0.238">66.221.0.238</a>:
OK:
2013073001 (124 ms)<br /><a href="http://ns8.baylink.com">ns8.baylink.com</a>.<br /> <a href="http://66.221.0.238">66.221.0.238</a>: OK: 2013073001 (125 ms)<br /></pre></blockquote></div><br>
-- <br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.</body></html>