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 fo
On Wed, Mar 2, 2011 at 1:38 PM, Wil Schultz 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
On Mar 2, 2011, at 11:17 AM, Christopher Morrow wrote:
> On Wed, Mar 2, 2011 at 1:38 PM, Wil Schultz 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 a
On Mar 3, 2011, at 2:42 AM, Wil Schultz wrote:
> Not a huge operational issue, but I'm sure there are some folks that this hit
> a little bit.
As Chris indicates, it would be a big win if recursion were disabled on the
authoritative servers, and instead handled by dedicated caching-only recurs
- Original Message -
> From: "Christopher Morrow"
> On Wed, Mar 2, 2011 at 1:38 PM, Wil Schultz
> 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'
On Mar 2, 2011, at 6:31 PM, Jay Ashworth wrote:
> - Original Message -
>> From: "Christopher Morrow"
>
>> On Wed, Mar 2, 2011 at 1:38 PM, Wil Schultz
>> wrote:
>>> ns1.twtelecom.net and ns2.twtelecom.net (along with some other DNS
>>> servers, ns1.orng.twtelecom.net and ns1.ptld.twtelec
6 matches
Mail list logo
