Are we allowed to change IP of a droplet outside the range?
It seems people use DigitalOcean droplets to launch DDoS attacks on servers around the world. A couple of the servers I am connecting to are managed by companies that run very large and popular data centers in Europe and Atlanta. These data centers block the IP ranges of both New York and Amsterdam droplets due to people launching DDoS attacks from them.
Now I am in a problem since I can’t connect due to DigitalOcean IPs being blacklisted by several major data centers around the world.
Is there any possibility that I can get a new public IP that is outside of the 107.170.*.* range? I know DigitalOcean New York has several different IP ranges. The 162.243.*.* range and several other ranges are unblocked. I am planning on launching an $80 instance for my production server and would like an IP range outside 107.170.*.* - For this very reason I have several droplets on digitalocean but I am using AWS EC2 for my connection to those servers.
These DDoSing people are really screwing things up for those who are using DigitalOcean legitimately.
I think it would be beneficial if you DigitalOcean allows us to choose an IP range rather than allotting us within a certain specific IP range and forcing us to use IPs within that range. I know you can generate a new IP by making a new droplet but that IP is always going to be in the BLACKLISTED range.
My Question is: Can I get a droplet within a different IP range preferably the 162.243.*.*? A couple of my colleagues have used this range have found it to be not blacklisted.
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.×