Distrowatch website

I haven't been able to get on to the distrowatch website for a few weeks now. I have tried Windows 10, Linux and Android smartphone. None of them will connect. I can connect from my works office and when my phone is set to mobile broadband. A friend has been round a couple of times and he cannot connect to distrowatch on his laptop at my house, but when he goes home he can connect immediately from the same laptop.
I just wondered if anyone else on Zen has the same problem before I contact Zen support?

I tried to post this question on the official Zen forums, but just got a permission denied message!

Nigel

This website? https://distrowatch.com/ Works fine here.

Yes works fine here as well.

Thank you for testing.

This is very odd. I will have to do some more investigation.

Nigel

Site works fine to me also.

Have you tried doing a lookup of the domain, ping it's IP and also trace routing to the server like shown below:

NSLookup:

# nslookup distrowatch.com

Server:  dns.google
Address:  2001:4860:4860::8888

Non-authoritative answer:
Name:    distrowatch.com
Addresses:  2a00:9080:1:20c::1
          82.103.136.226

Ping:

# ping -4 distrowatch.com

Pinging distrowatch.com [82.103.136.226] with 32 bytes of data:
Reply from 82.103.136.226: bytes=32 time=19ms TTL=52
Reply from 82.103.136.226: bytes=32 time=19ms TTL=52
Reply from 82.103.136.226: bytes=32 time=19ms TTL=52
Reply from 82.103.136.226: bytes=32 time=19ms TTL=52

Ping statistics for 82.103.136.226:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 19ms, Average = 19ms

Trace Route:

# tracert -4 distrowatch.com

Tracing route to distrowatch.com [82.103.136.226]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  YAZOO [192.168.2.253]
  2     1 ms     1 ms     1 ms  172.16.10.194
  3     3 ms     2 ms     2 ms  31.55.186.177
  4     3 ms     4 ms     3 ms  31.55.186.176
  5     3 ms     3 ms     3 ms  195.99.127.102
  6     3 ms     3 ms     3 ms  62.6.201.146
  7     2 ms     2 ms     2 ms  213.137.183.32
  8     3 ms     2 ms     3 ms  ldn-b9-link.telia.net [213.248.97.50]
  9     3 ms     3 ms     3 ms  ldn-bb4-link.telia.net [62.115.116.240]
 10    16 ms    15 ms    15 ms  hbg-bb4-link.telia.net [62.115.122.160]
 11    19 ms    19 ms    19 ms  kbn-bb4-link.telia.net [213.155.135.121]
 12    21 ms    21 ms    21 ms  kbn-b3-link.telia.net [62.115.121.13]
 13    22 ms    22 ms    22 ms  easyspeedy-ic-305269-kbn-b3.c.telia.net [62.115.40.174]
 14    19 ms    20 ms    19 ms  e82-103-136-226s.easyspeedy.com [82.103.136.226]

Trace complete.

You might be able to find the issue.
If you cannot ping or trace route using the domain name (might be a DNS issue) you can use their IP which is "82.103.136.226"

Also the -4 argument tells them to use IPv4, I have to do this due to my stupid Security Suit.

Paul

I use Linux Manjaro and use a DNS forwarder (dnsmasq running on Raspberry Pi)

nslookup distrowatch.com
Server: 192.168.11.80
Address: 192.168.11.80#53

Non-authoritative answer:
Name: distrowatch.com
Address: 82.103.136.226
Name: distrowatch.com
Address: 2a00:9080:1:20c::1

===================

ping -c 4 -4 distrowatch.com
PING distrowatch.com (82.103.136.226) 56(84) bytes of data.

--- distrowatch.com ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 34ms

================

traceroute -4 distrowatch.com
traceroute to distrowatch.com (82.103.136.226), 30 hops max, 60 byte packets
1 _gateway (192.168.11.1) 23.305 ms 22.516 ms 23.203 ms
2 192.168.1.1 (192.168.1.1) 23.802 ms 23.140 ms 23.113 ms
3 * * *
4 ae5-161.cr2.wh-man.zen.net.uk (62.3.86.13) 38.471 ms 43.032 ms 40.818 ms
5 * * *
6 * * *
7 * * *
8 ldn-b9-link.telia.net (62.115.169.134) 26.687 ms 25.219 ms 23.363 ms
9 ldn-bb4-link.telia.net (62.115.116.240) 30.782 ms 32.942 ms ldn-bb3-link.telia.net (62.115.117.6) 28.345 ms
10 hbg-bb4-link.telia.net (62.115.122.160) 36.202 ms 37.463 ms 38.567 ms
11 kbn-bb4-link.telia.net (213.155.135.121) 42.305 ms kbn-bb3-link.telia.net (213.155.130.101) 47.133 ms 49.225 ms
12 kbn-b3-link.telia.net (213.155.135.179) 43.050 ms kbn-b3-link.telia.net (80.91.252.23) 44.431 ms kbn-b3-link.telia.net (62.115.121.17) 45.299 ms
13 easyspeedy-ic-305269-kbn-b3.c.telia.net (62.115.40.174) 49.826 ms 47.554 ms 44.297 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

Nigel

Very odd that Paul's hop 13 and yours are identical. Yet his resolves on hop 14 and yours goes AWOL, with the same target address.

Edited by RobertoS (Tue 23-Jul-19 20:00:10)

Yeah its odd, I thought it was a routing issue, so maybe Zen are having some issues, maybe somebody else using Zen could check.

*** update ***
Also hop 13 looks like its the link between Telia's network and Easyspeedy's network, so might be an issue between them which is also odd due to its fine for me, maybe the OP IP is blacklisted and easyspeedy is blocking them?

Paul

Edited by PaulKirby (Tue 23-Jul-19 20:15:23)

I wondered if distrowatch have blocked a range of ip addresses and I happen to be included?
I cannot think of why they would. I just visit their site to read the latest Linux news once or twice a week.
I've never contacted distrowatch or criticised them so I can�t see I've upset them. In fact I think its a great site.

It's very strange.

Nigel

Are you using a Static IP with Zen or is it Dynamic?

If its Dynamic then maybe the person that had it before did some bad stuff.

But it might just be a routing issue, bit weird though.

*** update **
I also just tested the site via IPv6 (2a00:9080:1:20c::1) and IPv4 (82.103.136.226) both worked fine, so its not an IPv4 or IPv6 issue.

Paul

Edited by PaulKirby (Tue 23-Jul-19 21:11:56)