[DNS-Abuse-Measurements] abuse suspension of infrastructure domain names

Mon May 4 07:56:51 UTC 2020

Hello,

I think time (and so, money) is the most critical resource on all sides. From a RO perspective: Before taking down a domain name one *should* do some research to make sure that the abuse report is 1) evident, 2) the reason for taking down a domain name sufficient and 3) to communicate with the registrar for clarification to make sure that such things don’t happen.
Of course..this would be the ideal..

> Any ideas and feedback here to help us deal with such situations other than becoming a registrar ourselves?
First I suggest to talk to the registrar and try to establish better communication and processing regarding abusive domains in your portfolio.

Best, Matthias

On 27-4-2020 18:57, Andrey Nesterenko via DNS-Abuse-Measurements wrote:
Dear community,

I am a representative of a hosting service company. Today one of our domain names has been suspended by domain registrar because of spam abuse. The domain name is in fact infrastructure domain name which we used since 2005 for some dns servers and in server names.  Here is what happened - spam was sent from a hacked script on one the cPanel shared hosting servers.  And this server has this naming convention - sharedserver.$suspendeddomain.com

Of course, this domain name has nothing to do with that spam, but this suspension resulted in a major outage (fortunately not that long) for many services and customers in our global infrastructure.

I don't think it is a good idea to post here the domain name in question and corresponding registrar because my concern here is not how their abuse team handled that, but about some feedback from community and ICANN.

Would it be a good idea to protect such kind of domain names use in infrastructure of certain businesses from being suspended immediately for such low priority cases? There are a lot of companies like us who have just a few domain names important for DNS and resolving routing infrastructure tasks and they have to be protected somehow.

This is the second time it has happened to us so far.  The first time it was with .host registry a few years ago when they suspend another domain name used in our PaaS cloud infra: each environment had a domain name set up in such a way - env-123456.mircloud.host - exactly the same way as other cloud providers. Of course, it is possible that one of the customers can host phishing tools or viruses on such subdomains, but it should never mean to block the whole domain name entirely. That time it was blocked directly by Radix btw.

Any ideas and feedback here to help us deal with such situations other than becoming a registrar ourselves?

Andrey Nesterenko
MIRhosting

_______________________________________________

DNS-Abuse-Measurements mailing list

DNS-Abuse-Measurements at icann.org<mailto:DNS-Abuse-Measurements at icann.org>

https://mm.icann.org/mailman/listinfo/dns-abuse-measurements

_______________________________________________

By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/dns-abuse-measurements/attachments/20200504/b240274f/attachment-0001.html>