Bitcointalk no longer at 109.201.133.195 bitcointalk.org ?

[HITTI2]

Bitcointalk no longer at 109.201.133.195 bitcointalk.org ?

I had this

Code:

109.201.133.195 bitcointalk.org

in my hosts file on my pc, it would not connect. Theymos always said use your hosts to connect so if the forum gets taken, it will not connect unless it was from the ip 109.201.133.195.

I removed it and now I can connect to bitcointalk.

[deployuser]

Sites been hacked again?

[redsn0w]

Bitcointalk no longer at 109.201.133.195 bitcointalk.org ?

I had this

Code:

109.201.133.195 bitcointalk.org

in my hosts file on my pc, it would not connect. Theymos always said use your hosts to connect so if the forum gets taken, it will not connect unless it was from the ip 109.201.133.195.

I removed it and now I can connect to bitcointalk.

If I launch the command :

Code:

ping bitcointalk.org

it gives me :

root@redsn0w:~# ping bitcointalk.org
PING bitcointalk.org (186.2.165.183) 56(84) bytes of data.
64 bytes from node-186-2-165-183.reverse.x4b.me (186.2.165.183): icmp_seq=1 ttl=57 time=3.37 ms
64 bytes from node-186-2-165-183.reverse.x4b.me (186.2.165.183): icmp_seq=2 ttl=57 time=2.69 ms
64 bytes from node-186-2-165-183.reverse.x4b.me (186.2.165.183): icmp_seq=3 ttl=57 time=3.01 ms
^C
--- bitcointalk.org ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 2.695/3.028/3.375/0.277 ms

[wtogami]

The forum was under a big DDoS attack.  theymos has long resisted the idea of protecting the forum with the most cost effective DDoS protection providers like Cloudflare because doing so hands the SSL private keys to a 3rd party company and increases the privacy risk of the users.  Instead he decided to try hosting at another provider with automatic DDoS mitigation where theymos continues to directly control the SSL certificate.  He will see how things go with this new host provider.

[zcxvbs]

Bitcointalk no longer at 109.201.133.195 bitcointalk.org ?

I had this

Code:

109.201.133.195 bitcointalk.org

in my hosts file on my pc, it would not connect. Theymos always said use your hosts to connect so if the forum gets taken, it will not connect unless it was from the ip 109.201.133.195.

I removed it and now I can connect to bitcointalk.

If I launch the command :

Code:

ping bitcointalk.org

it gives me :

root@redsn0w:~# ping bitcointalk.org
PING bitcointalk.org (186.2.165.183) 56(84) bytes of data.
64 bytes from node-186-2-165-183.reverse.x4b.me (186.2.165.183): icmp_seq=1 ttl=57 time=3.37 ms
64 bytes from node-186-2-165-183.reverse.x4b.me (186.2.165.183): icmp_seq=2 ttl=57 time=2.69 ms
64 bytes from node-186-2-165-183.reverse.x4b.me (186.2.165.183): icmp_seq=3 ttl=57 time=3.01 ms
^C
--- bitcointalk.org ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 2.695/3.028/3.375/0.277 ms

Is it a temporary IP? I find I can't access the forum after the attacks too, the IP in my hosts files seems to be invalid, I need it to enable the connection to forum.

[thebitcoinquiz.com]

Bitcointalk no longer at 109.201.133.195 bitcointalk.org ?

I had this

Code:

109.201.133.195 bitcointalk.org

in my hosts file on my pc, it would not connect. Theymos always said use your hosts to connect so if the forum gets taken, it will not connect unless it was from the ip 109.201.133.195.

I removed it and now I can connect to bitcointalk.

If I launch the command :

Code:

ping bitcointalk.org

it gives me :

root@redsn0w:~# ping bitcointalk.org
PING bitcointalk.org (186.2.165.183) 56(84) bytes of data.
64 bytes from node-186-2-165-183.reverse.x4b.me (186.2.165.183): icmp_seq=1 ttl=57 time=3.37 ms
64 bytes from node-186-2-165-183.reverse.x4b.me (186.2.165.183): icmp_seq=2 ttl=57 time=2.69 ms
64 bytes from node-186-2-165-183.reverse.x4b.me (186.2.165.183): icmp_seq=3 ttl=57 time=3.01 ms
^C
--- bitcointalk.org ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 2.695/3.028/3.375/0.277 ms

Is it a temporary IP? I find I can't access the forum after the attacks too, the IP in my hosts files seems to be invalid, I need it to enable the connection to forum.

I don't think that its a temporary IP. Maybe theymos changed a bit of things after the DoS attach happened.
I guess the reason for the IP change is most probably related to the DoS attack. Only theymos could now clarify.

[theymos]

Changing IPs was necessary for DDoS protection. The forum will stay at this IP for a while, though probably not permanently. It probably won't return to 109.201.133.195.