On Mar 2, 2011, at 11:17 AM, Christopher Morrow wrote:
On Wed, Mar 2, 2011 at 1:38 PM, Wil Schultz <wschultz@bsdboy.com> wrote:
ns1.twtelecom.net and ns2.twtelecom.net (along with some other DNS servers, ns1.orng.twtelecom.net and ns1.ptld.twtelecom.net) suddenly stopped serving DNS for domains it's not authoritative for this morning. Requests are being actively refused from within their network.
Caused a small issue for us, just thought I'd pass along.
they were recursing previously and are no longer? that seems like a win... or did I misconstrue what you said?
They definitely do use ns1.twtelecom.net and ns2.twtelecom.net for hosting purposes (which probably shouldn't recurse), but they also generically recommend their clients to use them for recursion. Whatever the issue, all of their DNS servers that I tested lost the ability to recurse for about an hour. They are *mostly* working at this point, but not consistently. Not a huge operational issue, but I'm sure there are some folks that this hit a little bit.