Distrowatch

Not using Afrihost (on ECN Network), but also have issue so not isolated to Afrihost it seems.

1622458100176.png
 
Last edited:
AfriNatic said:
Which SMTP server are you using? the dsl mail one smtp.afrihost.co.za
Click to expand...

Dunno where that quote came from ... not the same as above.

My firewall box has caching DNS, supposed to use PiHole on a Pi Zero but does not atways. Think it's set to use 8.8.8.8 or maybe 1.1.1.1

Didn't know Afrihost (or Vuma, for that matter) did IP6 ... :)

I get similar rejection screen on Firefox, but works fine from UK ...

traceroute does not show anything weird but assume it's some network issue somewhere ...

thanks, Ian
 
iandoug said:
Dunno where that quote came from ... not the same as above.

My firewall box has caching DNS, supposed to use PiHole on a Pi Zero but does not atways. Think it's set to use 8.8.8.8 or maybe 1.1.1.1

Didn't know Afrihost (or Vuma, for that matter) did IP6 ... :)

I get similar rejection screen on Firefox, but works fine from UK ...

traceroute does not show anything weird but assume it's some network issue somewhere ...

thanks, Ian
Click to expand...

Might be a previous quote as it takes me to the issue you had with the SMTP server.

Which Vumatel are you using? Trenched with an Object number or Vuma GPON with a ONT?
 
iandoug said:
Trenched.
Durbanville, Cape Town
Click to expand...

Okay it's not supported on Vuma Trenched yet but is working on Vuma gpon since we are handling DHCP for that portion.

With regards to the issue you are experiencing can you do a trace route for me to distrowatch.com? I want to see where the traffic drops off.
 
That's the problem ... traceroute is fine.

traceroute to distrowatch.com (82.103.129.71), 30 hops max, 60 byte packets
1 ipfire (192.168.1.254) 0.230 ms 0.210 ms 0.209 ms
2 192.168.2.254 (192.168.2.254) 0.582 ms 0.835 ms 0.971 ms
3 165-73-112-1.ip.afrihost.capetown (165.73.112.1) 4.511 ms 4.827 ms 4.585 ms
4 169-1-2-132.ip.afrihost.capetown (169.1.2.132) 4.747 ms 11.418 ms 5.666 ms
5 169-1-2-113.ip.afrihost.capetown (169.1.2.113) 4.246 ms 4.247 ms 4.296 ms
6 169-1-21-147.ip.afrihost.co.za (169.1.21.147) 4.497 ms 4.087 ms 4.350 ms
7 169-1-21-131.ip.afrihost.co.za (169.1.21.131) 5.002 ms 5.070 ms 5.450 ms
8 wdcnw-os-cer-1-wan.osnet.co.za (196.25.158.241) 7.668 ms 4.333 ms 4.419 ms
9 10.189.30.34 (10.189.30.34) 161.967 ms 163.308 ms 161.779 ms
10 asergo.globalconnect-dk.nl-ix.net (193.239.118.94) 190.146 ms 190.223 ms 190.878 ms
11 e82-103-129-71s.asergo.com (82.103.129.71) 185.918 ms 190.091 ms 185.058 ms

DNSlytics says the IP is correct:

 
Suspect someone had a script running trying to boost pagehits on his favourite distro and they blacklisted a chunk of our IPs ...
 
iandoug said:
That's the problem ... traceroute is fine.

traceroute to distrowatch.com (82.103.129.71), 30 hops max, 60 byte packets
1 ipfire (192.168.1.254) 0.230 ms 0.210 ms 0.209 ms
2 192.168.2.254 (192.168.2.254) 0.582 ms 0.835 ms 0.971 ms
3 165-73-112-1.ip.afrihost.capetown (165.73.112.1) 4.511 ms 4.827 ms 4.585 ms
4 169-1-2-132.ip.afrihost.capetown (169.1.2.132) 4.747 ms 11.418 ms 5.666 ms
5 169-1-2-113.ip.afrihost.capetown (169.1.2.113) 4.246 ms 4.247 ms 4.296 ms
6 169-1-21-147.ip.afrihost.co.za (169.1.21.147) 4.497 ms 4.087 ms 4.350 ms
7 169-1-21-131.ip.afrihost.co.za (169.1.21.131) 5.002 ms 5.070 ms 5.450 ms
8 wdcnw-os-cer-1-wan.osnet.co.za (196.25.158.241) 7.668 ms 4.333 ms 4.419 ms
9 10.189.30.34 (10.189.30.34) 161.967 ms 163.308 ms 161.779 ms
10 asergo.globalconnect-dk.nl-ix.net (193.239.118.94) 190.146 ms 190.223 ms 190.878 ms
11 e82-103-129-71s.asergo.com (82.103.129.71) 185.918 ms 190.091 ms 185.058 ms

DNSlytics says the IP is correct:

Click to expand...

Hi Ian,

Are you still struggling to get get Distrowatch to load?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X