Update: information on microsoft takeover
Earlier today, we released some pot statement with Microsoft announcing the settlement from the unparalleled and overreaching seizure of 23 in our domains. We’re happy to announce the settlement of the dispute and therefore are excited to go back to work connecting our 18 million users for their website and devices.
How did this happen?
On Monday, June 30, 2014, Microsoft acquired an american order from the court to seize control in our most widely used domains utilized by both our Free that has been enhanced Dynamic DNS services. Consequently, nearly 5 million hostnames went dark and 1.8 million customer websites and devices grew to become unreachable.
Why did this happen?
Microsoft suspected a lot of our customers were mistreating our service for malicious purposes. However, rather of reporting the malicious activity to the abuse department or police force, Microsoft made the decision to secretly sue us in civil court.
Earlier today, we released some pot statement with Microsoft announcing the settlement from the unparalleled and overreaching seizure of 23 in our domains. We’re happy to announce the settlement of the dispute and therefore are excited to go back to work connecting our 18 million users for their website and devices.
How did this happen?
On Monday, June 30, 2014, Microsoft acquired an american order from the court to seize control in our most widely used domains utilized by both our Free that has been enhanced Dynamic DNS services. Consequently, nearly 5 million hostnames went dark and 1.8 million customer websites and devices grew to become unreachable.
Why did this happen?
Microsoft suspected a lot of our customers were mistreating our service for malicious purposes. However, rather of reporting the malicious activity to the abuse department or police force, Microsoft made the decision to secretly sue us in civil court.
By filing an ex parte temporary restraining order (TRO), No-IP was avoided from getting any understanding from the situation or offering any support in stopping malicious activity. Had Microsoft posted proof of abuse anytime, No-IP might have taken quick action to validate the claims and ban any accounts which were shown to be malicious. Rather, Microsoft wasted many several weeks while malicious activity ongoing.
To condition this as emphatically as you possibly can — this whole situation might have been prevented if perhaps Microsoft had adopted industry standards. A fast email or call towards the No-IP abuse team might have removed the abusive hostnames in the No-IP network.
Microsoft reported 22,000 hostnames which were abusive. From individuals 22,000 grabbed hostnames, no-IP abuse department found only a small fraction of the hostnames to be active, meaning many had recently been banned through our existing abuse procedures.
Microsoft guaranteed the judge they’d only block the hostnames purported to be malicious and would forward all of the remaining traffic for that non-abusive hostnames onto No-IP. This didn’t happen. The Microsoft DNS servers were misconfigured and unsuccessful to reply to our usual amount of vast amounts of queries each day.
On This summer 1 at 6:00 AM, Microsoft claimed to solve this error and reported that domains were fully operational.
Resourse: https://noip.com/blog/2014/07/10/microsoft-takedown-details-updates/
