It isn’t a Shaw problem
@CWLF -- Shaw's response was "not our problem".
Correct.
The two authoritative DNS-servers for that domain are "ns.namesv.com" and "ns2.namesv.com"
Asking one DNS-server for information about the domain:
$ nslookup -ty=any Elosoft.net ns2.namesv.com.
Server: UnKnown
Address: 216.19.64.214
Elosoft.net internet address = 216.19.79.1
Elosoft.net nameserver = ns.namesv.com
Elosoft.net nameserver = ns2.namesv.com
Elosoft.net MX preference = 10, mail exchanger = mail.Elosoft.net
Elosoft.net MX preference = 20, mail exchanger = smtp.Elosoft.net
ns.namesv.com internet address = 216.19.65.2
ns2.namesv.com internet address = 216.19.64.214
mail.Elosoft.net internet address = 216.19.65.2
smtp.Elosoft.net internet address = 216.19.65.2
Then, a trace to the IP-address ends with "time-out" ...
Tracing route to 216.19.79.1 over a maximum of 30 hops
4 10 ms rc1bb-be20.vc.shawcable.net [66.163.75.245]
5 14 ms rc1st-be25.vc.shawcable.net [66.163.69.198]
6 27 ms rc3no-be11-1.cg.shawcable.net [66.163.72.69]
7 42 ms rc2nr-be110-1.wp.shawcable.net [66.163.76.58]
8 67 ms rc3fs-be25.mt.shawcable.net [66.163.76.22]
9 64 ms bx4-toronto12_ge3-0-0.net.bell.ca [64.230.159.53]
10 68 ms tcore3-torontoxn_hundredgige0-1-0-0.net.bell.ca [64.230.97.156]
11 63 ms tcore3-toronto63_bundle-ether28.net.bell.ca [64.230.51.153]
12 64 ms agg2-oshawa95_xe7-0-0.net.bell.ca [64.230.48.27]
13 62 ms dis6-oshawa95_7-2-0.net.bell.ca [64.230.102.219]
14 * * * Request timed out.
It is not "reachable" from Bell's network in Oshawa.
So, it is either Bell's problem, or a problem (hardware failure?) at the domain.
I need to unblock goku.sx
@Satwinder268 Go to the BlueCurve app and turn off protected browsing (at your own risk).
@Satwinder268 -- I need to unblock ...
Hmm. The hyperlinks on that web-page:
* About Us
* Terms of service
* Contact
* Sitemap
each load a (random?) "spam" web-site. Definitely not a "safe" web-site.
Do you really have a "need" ?