jiyu_shi (OP)
Member
Offline
Activity: 81
Merit: 10
|
|
October 18, 2016, 12:35:38 AM |
|
I can't connect our forum by old /etc/host file: 45.55.191.107 ip.bitcointalk.org 54.235.199.197 bitcointalk.org
So, what's the new IP?
|
|
|
|
|
|
|
|
Whoever mines the block which ends up containing your transaction will get its fee.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
jerowacik
Legendary
Offline
Activity: 1162
Merit: 1000
|
|
October 18, 2016, 12:49:09 AM |
|
I see the IP from the command prompt in Windows functions. This is the IP address: 107.21.115.227
|
|
|
|
jiyu_shi (OP)
Member
Offline
Activity: 81
Merit: 10
|
|
October 18, 2016, 01:25:23 AM |
|
I see the IP from the command prompt in Windows functions. This is the IP address: 107.21.115.227
Thank you! Now I am login by 107.21.115.227.
|
|
|
|
John (John K.)
Global Troll-buster and
Legendary
Offline
Activity: 1288
Merit: 1226
Away on an extended break
|
|
October 18, 2016, 01:34:41 AM |
|
To get past a certain state-owned firewall, you can update your hosts file by using a ip resolver site like http://ip-lookup.net/domain.php . Do make sure it's the correct IP though as it's extremely easy to do a phishing attack should you use an outdated/malicious ip address.
|
|
|
|
jiyu_shi (OP)
Member
Offline
Activity: 81
Merit: 10
|
|
October 18, 2016, 01:47:22 AM |
|
To get past a certain state-owned firewall, you can update your hosts file by using a ip resolver site like http://ip-lookup.net/domain.php . Do make sure it's the correct IP though as it's extremely easy to do a phishing attack should you use an outdated/malicious ip address. Thank you. I almost ignored it. Of course, jerowacik is a good man.
|
|
|
|
coinableS
Legendary
Offline
Activity: 1442
Merit: 1179
|
|
October 18, 2016, 02:00:25 AM |
|
When I tried it earlier... ping bitcointalk.org
Pinging bitcointalk.org [107.21.115.227] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out.
Ping statistics for 107.21.115.227: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Checks out, that's bitcointalk alright!
|
|
|
|
jiyu_shi (OP)
Member
Offline
Activity: 81
Merit: 10
|
|
October 18, 2016, 02:21:35 AM |
|
It's normal to Bitcoin Forum ~$ ping -s 1 -c 1 bitcointalk.org PING bitcointalk.org (107.21.115.227) 1(29) bytes of data.
--- bitcointalk.org ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms
My trouble is: ~$ nslookup bitcointalk.org ;; Got SERVFAIL reply from xxx.xxx.xxx.xxx, trying next server Server: xxx.xxx.xxx.xxx Address: xxx.xxx.xxx.xxx#53
Non-authoritative answer: Name: bitcointalk.org Address: 8.7.198.45
What is 8.7.198.45? Is it Bitcoin Forum's IDC?
|
|
|
|
JeffBrad12
|
|
October 18, 2016, 04:39:16 AM |
|
When I tried it earlier... ping bitcointalk.org
Pinging bitcointalk.org [107.21.115.227] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out.
Ping statistics for 107.21.115.227: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Checks out, that's bitcointalk alright! Hahaha I got the same result with your, in my cmd is saying request timed out but in a really are running for smooth.... and what about that?
|
..Stake.com.. | | | ▄████████████████████████████████████▄ ██ ▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄ ██ ▄████▄ ██ ▀▀▀▀▀▀▀▀▀▀ ██████████ ▀▀▀▀▀▀▀▀▀▀ ██ ██████ ██ ██████████ ██ ██ ██████████ ██ ▀██▀ ██ ██ ██ ██████ ██ ██ ██ ██ ██ ██ ██████ ██ █████ ███ ██████ ██ ████▄ ██ ██ █████ ███ ████ ████ █████ ███ ████████ ██ ████ ████ ██████████ ████ ████ ████▀ ██ ██████████ ▄▄▄▄▄▄▄▄▄▄ ██████████ ██ ██ ▀▀▀▀▀▀▀▀▀▀ ██ ▀█████████▀ ▄████████████▄ ▀█████████▀ ▄▄▄▄▄▄▄▄▄▄▄▄███ ██ ██ ███▄▄▄▄▄▄▄▄▄▄▄▄ ██████████████████████████████████████████ | | | | | | ▄▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄ █ ▄▀▄ █▀▀█▀▄▄ █ █▀█ █ ▐ ▐▌ █ ▄██▄ █ ▌ █ █ ▄██████▄ █ ▌ ▐▌ █ ██████████ █ ▐ █ █ ▐██████████▌ █ ▐ ▐▌ █ ▀▀██████▀▀ █ ▌ █ █ ▄▄▄██▄▄▄ █ ▌▐▌ █ █▐ █ █ █▐▐▌ █ █▐█ ▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▀█ | | | | | | ▄▄█████████▄▄ ▄██▀▀▀▀█████▀▀▀▀██▄ ▄█▀ ▐█▌ ▀█▄ ██ ▐█▌ ██ ████▄ ▄█████▄ ▄████ ████████▄███████████▄████████ ███▀ █████████████ ▀███ ██ ███████████ ██ ▀█▄ █████████ ▄█▀ ▀█▄ ▄██▀▀▀▀▀▀▀██▄ ▄▄▄█▀ ▀███████ ███████▀ ▀█████▄ ▄█████▀ ▀▀▀███▄▄▄███▀▀▀ | | | ..PLAY NOW.. |
|
|
|
John (John K.)
Global Troll-buster and
Legendary
Offline
Activity: 1288
Merit: 1226
Away on an extended break
|
|
October 18, 2016, 05:23:36 AM |
|
It's normal to Bitcoin Forum ~$ ping -s 1 -c 1 bitcointalk.org PING bitcointalk.org (107.21.115.227) 1(29) bytes of data.
--- bitcointalk.org ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms
My trouble is: ~$ nslookup bitcointalk.org ;; Got SERVFAIL reply from xxx.xxx.xxx.xxx, trying next server Server: xxx.xxx.xxx.xxx Address: xxx.xxx.xxx.xxx#53
Non-authoritative answer: Name: bitcointalk.org Address: 8.7.198.45
What is 8.7.198.45? Is it Bitcoin Forum's IDC? If you're behind GFW that should be one of their fake addresses. GFW employs a DNS poisoning attack to hijack the location of blacklisted sites. That IP is a pretty common fake/misdirection IP that they use. You'll have to rely on external services to get the actual IP address for blocked sites.
|
|
|
|
|