Can you access to Distrowatch.com?

[mank_in]

If you can access website with Tor, but not with normal connection , the problem is with your ISP( maybe something like Internet censorship).
Maybe your ISP server run by Microsoft

[linuxviolin]

My ISP Box use Linux on it and on its network my provider normally uses stuff with it too. Also, I had no problem at all with same computers, the same OS's and at the same place to access distrowatch.com for years/months and suddenly since one or two months, poof, no more access to DistroWatch... Disappeared. All the others sites are OK.

@ Vincent Vermeulen

The output of the command 'dig distrowatch.com' :

Code: Select all

; <<>> DiG 9.8.1-P1-RedHat-9.8.1-4.P1.fc16 <<>> distrowatch.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7435
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;distrowatch.com.      IN   A

;; ANSWER SECTION:
distrowatch.com.   346   IN   A   66.180.174.35

;; Query time: 0 msec
;; SERVER: 192.168.0.254#53(192.168.0.254)
;; WHEN: Sun Jan 22 01:47:21 2012
;; MSG SIZE  rcvd: 49

[mank_in]

I think something weird with your router:

;; Query time: 0 msec
;; SERVER: 192.168.0.254#53(192.168.0.254)
;; WHEN: Sun Jan 22 01:47:21 2012
;; MSG SIZE rcvd: 49

its say Query time : 0 msec ( or you have very very super fast connection )
Maybe you can reconfigure/reset your router setting.

[glas]

Here's the dig command out put:

; <<>> DiG 9.7.0-P1 <<>> distrowatch.com
;; global options: +cmd
;; connection timed out; no servers could be reached


Just seems to state what the browser says. Or am I missing something?

[xenopeek]

@linuxviolin: The dig output shows your DNS does know the distrowatch.com site. It shows the correct IP address (66.180.174.35). Try:

Code: Select all

ping 66.180.174.35

If you don't get a response, install traceroute (sudo apt-get install traceroute) and:

Code: Select all

traceroute 66.180.174.35

Traceroute shows you each server your requests goes through before it reaches its destination. In my cases, it takes 17 hops before I reach distrowatch.com. You will probably get an error earlier, worth knowing/investigating at which hop it gets the error. If you share the output of it here, you may want to not post the first hop as this shows your IP address. The last hop I got:

17 ded135-fbsd-174-35.netsonic.net (66.180.174.35) 135.980 ms 136.463 ms 136.738 ms

@glas: Your output shows it the dig command can not reach your default DNS server. Either your internet connection was down, the DNS server was down, or it was misconfigured. Suggest you try the Google DNS instead:

Code: Select all

dig @8.8.8.8 distrowatch.com

[empusa]

I have been suffering the same problem with distrowatch.com for the last few days.
Having tried a few things out, it turned out to be a DNS problem. I'm not sure if any other sites are affected by this.
I changed my DNS servers to OpenDNS and it works now.
My ISP is TalkTalk in the UK. I assume that as it works on OpenDNS, TalkTalk must have inadvertently blacklisted distrowatch.com

[linuxviolin]

@linuxviolin: The dig output shows your DNS does know the distrowatch.com site. It shows the correct IP address (66.180.174.35). Try:

Code: Select all

ping 66.180.174.35

If you don't get a response...

Well, I get a response:

ping 66.180.174.35
PING 66.180.174.35 (66.180.174.35) 56(84) bytes of data.
64 bytes from 66.180.174.35: icmp_req=1 ttl=51 time=139 ms
64 bytes from 66.180.174.35: icmp_req=2 ttl=51 time=143 ms
64 bytes from 66.180.174.35: icmp_req=3 ttl=51 time=143 ms
64 bytes from 66.180.174.35: icmp_req=4 ttl=51 time=142 ms
64 bytes from 66.180.174.35: icmp_req=5 ttl=51 time=141 ms
64 bytes from 66.180.174.35: icmp_req=6 ttl=51 time=140 ms
64 bytes from 66.180.174.35: icmp_req=7 ttl=51 time=139 ms
64 bytes from 66.180.174.35: icmp_req=8 ttl=51 time=145 ms
64 bytes from 66.180.174.35: icmp_req=9 ttl=51 time=143 ms
64 bytes from 66.180.174.35: icmp_req=10 ttl=51 time=143 ms
64 bytes from 66.180.174.35: icmp_req=11 ttl=51 time=142 ms
64 bytes from 66.180.174.35: icmp_req=12 ttl=51 time=141 ms
64 bytes from 66.180.174.35: icmp_req=13 ttl=51 time=139 ms
64 bytes from 66.180.174.35: icmp_req=14 ttl=51 time=143 ms
64 bytes from 66.180.174.35: icmp_req=15 ttl=51 time=142 ms
64 bytes from 66.180.174.35: icmp_req=16 ttl=51 time=143 ms
^C
--- 66.180.174.35 ping statistics ---
16 packets transmitted, 16 received, 0% packet loss, time 15019ms
rtt min/avg/max/mdev = 139.387/142.253/145.030/1.720 ms

EDIT: Miracle! I just try again and hop the problem seems solved, at least in this Linux box! After about two months and with no action from me! I should try now with my other(s) PC and in my other OS's. incredible!

[glas]

Congratulations on fixing the problem linxviolin. BTW, how did you fix it?

My ping results are the same.

Here's another output:

mint@mint-desktop ~ $ dig @8.8.8.8 distrowatch.com

; <<>> DiG 9.7.0-P1 <<>> @8.8.8.8 distrowatch.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60452
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;distrowatch.com. IN A

;; ANSWER SECTION:
distrowatch.com. 819 IN A 66.180.174.35

;; Query time: 36 msec
;; SERVER: 8.8.8.8#53(8.8.8.
;; WHEN: Sun Jan 22 21:46:31 2012
;; MSG SIZE rcvd: 49


still can't connect!

but thanks for the ideas

[linuxviolin]

Congratulations on fixing the problem linxviolin. BTW, how did you fix it?

Well, this is the miracle as I did nothing at all! Since about two months I had no more access to distrowatch.com and boom tonight the access is reappeared with no action from me, as I said in my last post. The only thing I did tonight is the ping command: ping 66.180.174.35 I don't understand. But I must still try also on my other(s) PC(s) with other OS's (Linux and Windows) to see if the access is reappeared there too.

[aliashh]

I have been unable to access distrowatch for about a week now from 3 pc's - 1 mint and 2 win xp. Using firefox or chrome on the mint m/c a page opens full of adverts but in chinese. Using ie, firefox, or chrome on xp an "unobtainable" message appears. My b/b provider is talktalk who where able to access distrowatch at the call centre but were no help and a friend also on talktalk had no problem. I have flushed the dns and cleared the cache with no joy.
Anybody got any ideas ?

[xenopeek]

I have been unable to access distrowatch for about a week now from 3 pc's - 1 mint and 2 win xp. Using firefox or chrome on the mint m/c a page opens full of adverts but in chinese. Using ie, firefox, or chrome on xp an "unobtainable" message appears. My b/b provider is talktalk who where able to access distrowatch at the call centre but were no help and a friend also on talktalk had no problem. I have flushed the dns and cleared the cache with no joy.
Anybody got any ideas ?

I'd suspect a virus if you only had Windows machines... Do all computers connect to your broadband modem directly (or through wifi), or is there some other shared device all these computers use to get to the internet? If http://66.180.174.35 doesn't get you to distrowatch, then perhaps your broadband modem has been hacked. Might be worth checking with TalkTalk if you can do a hardware reset of the firmware settings, or if they can push a clean firmware remotely.

[aliashh]

All three m/cs wired to a huwai router. I had pinged www.distrowatch.com with no joy but pinging 66.180.174.35 got a response, which I couldn't fathom. I have now changed to opendns with success so the problem must have been a dns resolve somewhere along the line.

[xenopeek]

See also this topic over at the TalkTalk forums: http://www.talktalkmembers.com/forums/s ... hp?t=75373