[PLUG] Reality check

Russell Senior russell at personaltelco.net
Sun Nov 19 05:34:41 UTC 2017


On Nov 18, 2017 9:32 PM, "Tom" <tomas.kuchta.lists at gmail.com> wrote:

I can reach both web sites, not sure about the list.

It is not unusual that computers do not respond to ping these days.

Perhaps you can try: traceroute lists.opendkim.org
Traceroute does not guarantee anything either, but at least show if
there is some sort of network route to IP.


Tcptraceroute is pretty reliable, because the probes are indistinguishable
from a normal connection attempt.


ping www.opendkim.org
PING medusa.blackops.org (208.69.40.157) 56(84) bytes of data.
64 bytes from medusa.blackops.org (208.69.40.157): icmp_seq=1 ttl=54
time=22.1 ms
www.verizonwireless.com does not respond to ping but loads in browser.
lists.opendkim.org does not respond to ping or traceroute.

traceroute to lists.opendkim.org (208.69.177.116), 30 hops max, 60 byte
packets
 1  usg1 (192.168.1.1)  0.412 ms  0.576 ms  0.389 ms
 2  ptld-dsl-gw49.ptld.qwest.net (207.225.84.49)  3.347 ms  3.507
ms  3.776 ms
 3  ptld-agw1.inet.qwest.net (207.225.86.129)  3.594 ms  3.708
ms  3.808 ms
 4  sea-brdr-02.inet.qwest.net (67.14.41.190)  7.126 ms  7.223
ms  7.519 ms
 5  be209.ccr21.sea02.atlas.cogentco.com (154.54.11.1)  23.969
ms  23.855 ms  25.295 ms
 6  be2084.ccr22.sea01.atlas.cogentco.com (154.54.0.253)  24.450 ms
be2083.ccr21.sea01.atlas.cogentco.com (154.54.0.249)  21.590 ms
be2084.ccr22.sea01.atlas.cogentco.com (154.54.0.253)  22.125 ms
 7  be2075.ccr21.sfo01.atlas.cogentco.com (154.54.0.233)  24.792
ms  24.723 ms  24.601 ms
 8  be3178.ccr21.sjc01.atlas.cogentco.com (154.54.43.70)  24.814 ms
be3179.ccr22.sjc01.atlas.cogentco.com (154.54.43.150)  22.224
ms  22.089 ms
 9  be2063.rcr21.b001848-1.sjc01.atlas.cogentco.com
(154.54.1.162)  22.693 ms be2095.rcr21.b001848-
1.sjc01.atlas.cogentco.com (154.54.3.138)  23.589 ms  23.997 ms
10  * * *
11  * * *
........

Check if DNS works by asking dig or nslookup

For basic sanity checks, I found www.google.com to respond reliably to
ping. Additionally it is good for checking DNS as it should change IP
with most requests.

Tomas

On Sat, 2017-11-18 at 15:47 -0800, Rich Shepard wrote:
>    With the mail/phone issues I've had recently I want to check that
> I'm
> doing things correctly. Two instances of not reaching
> web pages.
>
>    I can load (and ping) www.opendkim.org, but cannot load (or ping)
> lists.opendkim.org. This means their mail list page is off-line. Yes?
>
>    Yesterday and today I try to access www.verizonwireless.com but
> the page
> won't load. Neither can I ping that server. This means that their web
> site
> is down. Yes?
>
>    Perhaps it's the fault of climate change, but the mail server for
> the LyX
> mail list has been down for 8 days now "we have some hardware issues
> that
> should be resolved soon." Definition of 'soon' is left to the reader.
>
> Rich
> _______________________________________________
> PLUG mailing list
> PLUG at pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
_______________________________________________
PLUG mailing list
PLUG at pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug



More information about the PLUG mailing list