I can't even ping from here or have I missed something along the way? bash-4.1# ping torfree.net ping: unknown host torfree.net bash-4.1# bash-4.1# ping freenet.toronto.on.ca ping: unknown host freenet.toronto.on.ca bash-4.1# -- Slackrat
On 25/03/15 06:00 PM, SlackRat wrote:
I can't even ping from here
or have I missed something along the way?
bash-4.1# ping torfree.net ping: unknown host torfree.net bash-4.1# bash-4.1# ping freenet.toronto.on.ca ping: unknown host freenet.toronto.on.ca bash-4.1#
http://isup.me/torfree.net "It's not just you! http://torfree.net looks down from here."
Looks like a dns problem $ nslookup torfree.net nslooku;; connection timed out; trying next origin p ;; connection timed out; no servers could be reached $ nslookup freenet.toronto.on.ca Server: 64.71.255.204 Address: 64.71.255.204#53 ** server can't find freenet.toronto.on.ca: NXDOMAIN On 03/25/2015 06:13 PM, Blaise Alleyne wrote:
On 25/03/15 06:00 PM, SlackRat wrote:ping torfree.net
ping torfree.net I can't even ping from here
or have I missed something along the way?
bash-4.1# ping torfree.net ping: unknown host torfree.net bash-4.1# bash-4.1# ping freenet.toronto.on.ca ping: unknown host freenet.toronto.on.ca bash-4.1#
"It's not just you! http://torfree.net looks down from here."
--- Talk Mailing List talk@gtalug.org http://gtalug.org/mailman/listinfo/talk
-- David Collier-Brown, | Always do right. This will gratify System Programmer and Author | some people and astonish the rest davecb@spamcop.net | -- Mark Twain
David Collier-Brown wrote:
Looks like a dns problem $ nslookup torfree.net nslooku;; connection timed out; trying next origin p ;; connection timed out; no servers could be reached
Relevant records per gtld-servers: ;; AUTHORITY SECTION: torfree.net. 172800 IN NS ns.torfree.net. torfree.net. 172800 IN NS ns2.torfree.net. ;; ADDITIONAL SECTION: ns.torfree.net. 172800 IN A 204.225.122.149 ns2.torfree.net. 172800 IN A 204.225.122.150 which shows they put both eggs in the same basket network-wise; traceroute from two locations both go into the weeds somewhere in Convoke's network, their apparent upstream. Notably the crosstoown traceroute ends in: 8 convoke.ip4.torontointernetxchange.net (206.108.34.51) 3091.818 ms !H 3098.879 ms !H 3079.178 ms !H which says they _were_ on the other side of that router at TorIX and it's probably unsuccessfully ARPing the nexthop.
$ nslookup freenet.toronto.on.ca Server: 64.71.255.204 Address: 64.71.255.204#53
** server can't find freenet.toronto.on.ca: NXDOMAIN
CIRA's whois server denies knowledge of that domain, though back in the dark ages that was the name format their predecessors foisted on people. -- Anthony de Boer
Colin write to say they had a multiple drive failure, and are repairing as we speak --dave On 03/25/2015 06:13 PM, Blaise Alleyne wrote:
On 25/03/15 06:00 PM, SlackRat wrote:
I can't even ping from here
or have I missed something along the way?
bash-4.1# ping torfree.net ping: unknown host torfree.net bash-4.1# bash-4.1# ping freenet.toronto.on.ca ping: unknown host freenet.toronto.on.ca bash-4.1#
"It's not just you! http://torfree.net looks down from here."
--- Talk Mailing List talk@gtalug.org http://gtalug.org/mailman/listinfo/talk
-- David Collier-Brown, | Always do right. This will gratify System Programmer and Author | some people and astonish the rest davecb@spamcop.net | -- Mark Twain
participants (4)
-
Anthony de Boer -
Blaise Alleyne -
David Collier-Brown -
SlackRat