BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

DNS went haywire yesterday?

Subject: DNS went haywire yesterday?
From: bobleigh at twomeeps.com (Bob Leigh)
Date: Mon, 17 Nov 2003 15:59:10 -0500
In-reply-to: <7525.66.31.42.38.1069101186.squirrel@envoy.ci.net>; from richb@pioneer.ci.net on Mon, Nov 17, 2003 at 03:33:06PM -0500

Rich Braun <richb at pioneer.ci.net> wrote:
> Perhaps if some of y'all Comcast users would help me gang up on them.  Try
> nslookup or dig of your own dynamic IP and see if it sits there hanging for
> 10+ seconds.  At the moment, mine returns NXDOMAIN (as opposed to
> <foo>.client2.attbi.com like it used to) after a server timeout.

Nope, mine gives the usual h8000xxxxxxxx.ne.client2.attbi.com -- in 5ms
if I believe dig. ;-)

-- 
Bob Leigh	bobleigh at twomeeps.com

Follow-Ups:
- DNS went haywire yesterday?
  - From: junkforjerry at hotmail.com (jerry miu)

References:
- DNS went haywire yesterday?
  - From: richb at pioneer.ci.net (Rich Braun)

Prev by Date: scripting "interactive" input
Next by Date: DNS went haywire yesterday?
Previous by thread: DNS went haywire yesterday?
Next by thread: DNS went haywire yesterday?
Index(es):
- Date
- Thread


BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Boston Linux & Unix / webmaster@blu.org