Dear Customers,We have added a few new features to our control panel:
Support for SSHFP records
Now you can secure your SSH at DNS level. SSHFP record is available for Master (Primary) and Slave (Secondary) DNS zones.
Option to delete a DNS zone from the Records page
It's easy to find a DNS zone with the search option from the Dashboard, but it wasn't so easy to delete it. Now if you have 1000+ DNS zones and you want to delete one of them, you can find the zone with the search and delete it from the button at the Records page.
Option to move a DNS zone to another accout
If you sell any of your domain names and want to move the DNS settings to another account (e.g. of your customer), you just need his e-mail address.
Option to import records in Master DNS zone from external Master DNS server
If you allow the zone transfers for www.cloudns.net (184.108.40.206), you will be able to import records from this remote server to your Master DNS zone here. When you send the request to the other DNS server, you will see a list with all DNS records and option to add them. The feature is available in the right menu of the DNS zone control panel with the records.
We are starting June Domain Promotion for new domain registrations:
For every domain registration you will receive 1 month free Premium account extension!
The promotion is active until the end of June.Regards,
ClouDNS Sales Team
For the last 5 days DNS servers pns1.cloudns.net, pns2.cloudns.net, pns3.cloudns.net and pns4.cloudns.net are under large DDoS attacks (over 25Gbps and 2,000,000 packages per second). From the beginning of the attack pns1.cloudns.net and pns4.cloudns.net are null routed, because of a limited capacity of the data centers in the United Kingdom and Romania.Mitigation strategy
pns1.cloudns.net is restored to normal activity.
pns2.cloudns.net is with changed IP - 220.127.116.11 (old IP is 18.104.22.168). The service is provided by DDoS Guard and is with 140Gbps capacity. It should be able to handle this big attack against our service.
pns3.cloudns.net is with unchanged IP address. It is backed by Staminus (one of the largest DDoS protection providers). The limit of the protection is 5Gbps. We will upgrade it soon.
pns4.cloudns.net is forwarded to the new pns2.cloudns.net server.
pns6.cloudns.net is with changed IP - 22.214.171.124 (old IP is 126.96.36.199). The new server is located again in Texas, USA.
If you use Slave DNS zones, you need to allow the new IP addresses of pns2.cloudns.net and pns6.cloudns.net for zone transfers. Currently all Slave DNS zones are migrated with their last state.
If you use DNS branding, you need to upgrade your A and Glue records to the new pns2.cloudns.net and pns6.cloudns.net IP addresses.
The old IP addresses of pns2.cloudns.net and pns6.cloudns.net will be supported until Jun 1, 2014.1,000% SLA
According to our 1,000% SLA all our customers with these servers are extended with 50 days for free.
Sorry for the caused inconvenience. Please contact us, if you have any problems.
[RESOLVED] pns1.cloudns.net, pns2.cloudns.net, pns3.cloudns.net and pns4.cloudns.net are under a large DDoS Attack2014-04-18
pns1.cloudns.net and pns4.cloudns.net are temporary down, because of a large DDoS attack (over 30Gbps).
[UPDATE 16:34 CET] pns1.cloudns.net is currently okay. Attack is moved to pns2.cloudns.net and pns3.cloudns.net. To prevent damades our Romanian data center null-routed pns4.cloudns.net
[UPDATE 19:21 CET] Everything is okay from 2 hours on pns2.cloudns.net and pns3.cloudns.net. We work to get pns1.cloudns.net back up.
[UPDATE 21:20 CET] ns2.cloudns.net is included to the list with attacked servers.
[UPDATE Apr 19, 16:00 CET] pns1.cloudns.net and pns4.cloudns.net are still null-routed. We will try to get pns1.cloudns.net back up after few hours.
[UPDATE Apr 19, 20:00 CET] The Attack continues with full power. pns1.cloudns.net, pns2.cloudns.net, pns3.cloudns.net and pns4.cloudns.net are attacked with over 20Gbps
[UPDATE Apr 20, 20:00 CET] Everything with the attack is okay now. pns4.cloudns.net is still nullrouted to be save data center in Romania. pns3.cloudns.net is in the Staminus data center in their Irvine DC and currently is down, because an outage of the data center. The problem is related with the fiber connection and it is not related with our attack.
[UPDATE Apr 21, 05:00 CET] The problem of Staminus Irvine DC is fixed. pns3.cloudns.net is back up and everything looks okay. If everything is okay today, we will remove the nullroute of pns4.cloudns.net and add it back to the cloud.
[UPDATE Apr 21, 9:45 CET] The attack started again. pns1.cloudns.net and pns4.cloudns.net are nullrouted.
[UPDATE Apr 22, 7:30 CET] pns1.cloudns.net and pns4.cloudns.net are forwarded to pns3.cloudns.net and pns2.cloudns.net is forwarded to ns1.cloudns.net. We work to mitigate the attack with third party services like BlackLotus and Staminus. More information will be added soon.
[UPDATE Apr 22, 10:45 CET] The IP address of pns2.cloudns.net is changed to 188.8.131.52. The owners of slave (Secondary) DNS zones need to add this IP to their list with allowed master servers for transfers. The customers with DNS branding should update it too. Customers with Master DNS zones don't need to change their settings. The service behind this IP is provided by DDoS Guard.Regards,
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,