BLU Discuss list archive

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

Diagnosing connection issue

Subject: Diagnosing connection issue
From: edwardp-jjFNsPSvq+iXDw4h08c5KA at public.gmane.org (edwardp-jjFNsPSvq+iXDw4h08c5KA at public.gmane.org)
Date: Mon, 14 Feb 2011 09:09:07 -0500
In-reply-to: <8CD9A5FC4F16172-11EC-271E4-n3SY6/QrmYVzucvt8Fh30bQXJ8qk6zCwQQ4Iyu8u01E@public.gmane.org>
References: <8CD9A5FC4F16172-11EC-271E4@webmail-d031.sysops.aol.com>

Sorry for the blank message earlier.  Currently using a quirky mobile 
interface.

It did not matter which DNS was used, it occurred using default 
Comcast, Comcast DNSSEC, as well as Google's DNS service.  This is what 
makes it more strange...

References:
- Diagnosing connection issue
  - From: edwardp-jjFNsPSvq+iXDw4h08c5KA at public.gmane.org (edwardp-jjFNsPSvq+iXDw4h08c5KA at public.gmane.org)

Prev by Date: Diagnosing connection issue
Next by Date: Linux for non-CMOV processors
Previous by thread: Diagnosing connection issue
Next by thread: Diagnosing connection issue
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