Mailing List Archive

Possible comcast.net DNS botch?
It appears to me that at the moment (2:45 PM EDT) that comcast.net is
not resolving. (I noticed this while checking a mail queue; oldest
entry in that queue outbound for Comcast is from 1:40 AM today.)
A very preliminary (and thus likely inaccurate) check of DNS suggests
to me that perhaps the glue records are missing at Verisign; neither
ns21.worldnic.com nor ns22.worldnic.com seems to know anything about
comcast.net at the moment.

I'd like to request that someone check my observations and reasoning
on this (doubly so since I've been awake for quite some time and am thus
particularly error-prone).

---Rsk
Possible comcast.net DNS botch? [ In reply to ]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Rich Kulawiec wrote:
> It appears to me that at the moment (2:45 PM EDT) that comcast.net is
> not resolving. (I noticed this while checking a mail queue; oldest
> entry in that queue outbound for Comcast is from 1:40 AM today.)
> A very preliminary (and thus likely inaccurate) check of DNS suggests
> to me that perhaps the glue records are missing at Verisign; neither
> ns21.worldnic.com nor ns22.worldnic.com seems to know anything about
> comcast.net at the moment.

Domain was hijacked:

http://www.theregister.co.uk/2008/05/29/comcast_domain_hijacked/



- --
Chris Stone, MCSE
Vice President, CTO
AxisInternet, Inc.
http://www.axint.net
DSL, dialup, hosting, email filtering, co-location, online backup
Phone: +1 303 592 2947 x302 (office) +1 303 570 6947 (cell)
- -------------------------------------------------------------------------

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org

iEYEAREKAAYFAkg/TZgACgkQnSVip47FEdPNegCfZG6k0dr/q3ncFGI7OGqNnlNY
WcMAnj++fke3TDmaducK7qT+di6x0c3K
=fY3w
-----END PGP SIGNATURE-----
Possible comcast.net DNS botch? [ In reply to ]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- -- Rich Kulawiec <rsk at gsp.org> wrote:

>It appears to me that at the moment (2:45 PM EDT) that comcast.net is
>not resolving. (I noticed this while checking a mail queue; oldest
>entry in that queue outbound for Comcast is from 1:40 AM today.)
>A very preliminary (and thus likely inaccurate) check of DNS suggests
>to me that perhaps the glue records are missing at Verisign; neither
>ns21.worldnic.com nor ns22.worldnic.com seems to know anything about
>comcast.net at the moment.
>
>I'd like to request that someone check my observations and reasoning
>on this (doubly so since I've been awake for quite some time and am thus
>particularly error-prone).
>

There may have been a "quick fix" of some kind, just to get
comcast.net to resolve properly (caveat: I haven't checked).

As an aside, a couple of teenagers are about to spanked over
this little stunt:

http://blog.wired.com/27bstroke6/2008/05/comcast-hijacke.html

- - ferg

-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.6.3 (Build 3017)

wj8DBQFIP06lq1pz9mNUZTMRAhePAKCGSJ+64idvRXEYZLX1aifRRZj2ZgCg+3CE
Ho1vHlqGgKV6L0nsD6CnSXY=
=cUgs
-----END PGP SIGNATURE-----


--
"Fergie", a.k.a. Paul Ferguson
Engineering Architecture for the Internet
fergdawg(at)netzero.net
ferg's tech blog: http://fergdawg.blogspot.com/