Question

Digial Ocean Servers IP blacklisted

Hi.

I have set up 2 droplets with Digital Ocean now and both have had IP addresses appear as blacklisted which has resulted in email not getting through to a clients email. I have raised ticket with Digital Ocean and on both occasions I have been informed I will need to generate another droplet

Both instances are Ubuntu 12.10 x64

Has anyone else experienced any issues with blacklisting like this. That is 2 consecutive IP addresses that have been blacklisted and I am wondering whether there is a vulnerability or some issue in the set up of the sever. The Digital Ocean prices and ease of use are a big pull for me but I am loathed to spin up another VPS and disrupt a clients website for the 3rd time in 2 weeks if I am going to experience the same issue. At the moment I am considering cancelling my account and switching to another provider such as bytemark.

Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

IP addresses get blacklisted for a number of reasons, however the real challenge is getting off these blacklists. With a little effort, and patience it is however not impossible. Just find out who’s blacklisting, and contact those providers to first identify the reason, and learn what you’ll need to do in order to be removed. <br> <br>You’ll find most providers if approached correctly, will work with you to remove you from a blacklist, unless ofcourse you caused the IP to be blacklisted. Also make sure if you’re letting clients use your droplet(s) for email, that they are not triggering the blacklisting. <br> <br>It’s also a good idea to subscribe to provider “Feedback Loops” so that you can track complaints, and address them accordingly. <br> <br>I deal with blacklisting issues at least once every 3 - 4 months as a result of a server which sends out a large amount of email, though annoying to deal with, you learn a lot, and actually build good relations in the process when you’re willing to take the time to deal with these matters. <br> <br>-Peter

Hello there,

DNSBL blacklists can mark whole IP ranges indeed. This is really annoying as often it has nothing to do with your own mail reputation but you’ll still be affected.

Stopping spam is a constant fight, so we have implemented some restrictions on newer accounts, but this still does not guarantee all SPAM will be stopped.

In the meantime, you can use a site like MXtoolbox to check the mail reputation of your IP and send an email to https://mail-tester.com

Their tool will show how you can improve your mail score (outgoing mail delivery).

You can also use a third party mail provider like SendGrid in order to avoid issues like this one. I’ll also recommend checking this article:

https://www.digitalocean.com/community/tutorials/why-you-may-not-want-to-run-your-own-mail-server

You can reach to our support team as well regarding the mail reputation of the whole range.

https://www.digitalocean.com/support/

Hope that this helps!

<b>“I am wondering whether there is a vulnerability…”</b> <br> <br>This could very well be. <br> <br><b>“The Digital Ocean prices and ease of use are a big pull…”</b> <br> <br>For a segment of folks that have never tinkered with – let alone managed – a server before. In other words, DO’s low price point will attract a lot of people that don’t know what they’re doing and/or people that casually employ lax security measures b/c a compromised server can be easily destroyed (at no additional cost) and a new server can be spun-up from a snapshot or backup (at no additional charge). <br> <br>For example, a mail server can easily end up blacklisted if the <code>/etc/hosts</code> file is not properly set to reflect the server’s Fully Qualified Domain Name. For instructions on how to properly configure the <code>/etc/hosts</code> file, check out <a href=“https://github.com/DigitalOcean-User-Projects/Articles-and-Tutorials/blob/master/set_hostname_fqdn_on_ubuntu_centos.md”>Setting the Hostname & Fully Qualified Domain Name (FQDN) on Ubuntu 12.04 or CentOS 6.4 | GitHub</a>. <br> <br>As Peter noted, if you discern with whom your IPs are blacklisted, you can get things cleared up by contacting the company/service provider that maintains the blacklist, directly.