[RESOLVED] Emergency synchronization2014-04-11
Because of a required emergency synchronization of some of our servers, it is possible the updates to be delayed. We are sorry for the caused inconvenience.
[UPDATE 18:45 CET] Emergency synchronization is completed. Please contact our technical support, if you have any problems questions.Regards,
Heartbleed OpenSSL Vulnerability Notification2014-04-10
We have received a few questions related with this vulnerability. We want to inform you that our servers are not affected by Heartbleed vulnerability. So please don't panic and enjoy your service.Regards,
Primary and Secondary Reverse DNS zones2014-04-08
Today we release the long requested feature Registering of Reverse DNS Zones. Every Premium customer now can register IPv4 or IPv6 Master or Slave Reverse Zone and can add NS and PTR records to it. The Reverse DNS is also available with several API methods. You can find out, if an API method supports Reverse zones on its API help page.
Wire Transfers are added to the payment methods. Our bank account is in EU, so for the customers in EU the SEPA fees should be very low.
Don't hesitate to contact us, if you have any problems or questions.Regards,
[RESOLVED] dns1.cloudns.net is experiencing a hardware problem2014-04-05
DNS1.cloudns.net is experiencing a hardware problem. We are working to solve the problem.
[UPDATE 2014-04-06 07:00 CET] The problem is fixed by the team in the data centre and server is back up.
[UPDATE 2014-04-06 15:30 CET] The server is down again. It looks like a problem with fans. The team in the data center work on this.
[UPDATE 2914-04-07 00:50 CET] The server is replaced with new one. Harddrives are moved to the new server and all DNS zones are up to date.
[RESOLVED] DDoS attack - ns1, ns2, ns3 and ns4.cloudns.net2014-03-23
Free DNS servers ns1.cloudns.net, ns2.cloudns.net, ns3.cloudns.net and ns4.cloudns.net are under a large DDoS attack. We work to mitigate it.
We will keep you updated. Sorry for the inconvenience.
[Update 2014-03-24 8:00CET] DDoS attack is mitigated on ns1.cloudns.net. We work to mitigate it at all.