Janet to us
- Jan 25, 2006
- Reaction score
- Work.... Where else?
I dont see how, as you would change the IP of the server which is what they will be blocking. If they're blocking the DNS then it's pointless, you just change the DNS as well. The whole point of hiding behind a CDN is so that they cannot see your real IP, therefore they cannot block it, only the IP they're seeing from the CDN. They're likely blocking the DNS that way, but again, you simply rotate the DNS and it's unblocked.Hiding behind flare and AWS does not work anymore.
The only way they can 100% block anything is via IPv6 as each individual device then has it's own IP, which is individual to that device. Until all ISPs start using it then it's a futile task of whack-a-mole. Once IPv6 is implemented, then it's a whole different ball game.
The whole Russia blocking telegram proves that the AWS thing works, they blocked I think it was 16 million IPs and still couldn't shutdown telegram. They lost a whole lot of other services in the process as well, there aren't enough IPs to go around so you have to use NAT/PAT and that causes them issues, as they cannot block individual IPs.
The problem you have is that Cloudflare are likely assisting via DCMA takedowns, so it's them taking the service down, and not the server being blocked per se.