status

We are re-assigning the IP addresses for remote1.easydns.com and remote2.easydns.com. The changes will be as follows; WAS remote1.easydns.com 216.246.59.66 remote2.easydns.com 209.200.141.4 IS NOW remote1.easydns.com 205.234.220.154 remote2.easydns.com 209.200.187.4 This will not impact name service resolution, although if you are a secondary customer and are using a DNS server that can not accept netblock assignments into the […]

Just over an hour ago, the co-location facility we use in Amsterdam suffered a brief power outage, which resulted in two of our nameservers being unexpectedly restarted: ams1.easydns.com (part of the “ns1.easydns.com” Anycast cluster) ns6.easydns.net Our sysAdmins took “ams1.easydns.com” out of the “ns1.easydns.com” Anycast cluster as soon as this occurred, which means that “ns1.easydns.com” was […]

We’ve changed the glue record in the roots for ns3.easydns.org to reference a different node while we debug the data syncing issue. Some queries are still coming in owing to DNS cache issues. If you recently updated your zone and that update has not been reflected in ns3.easydns.org then you could also consider removing ns3.easydns.org […]

We’re experiencing issues with this machine updating zone info. We are working to resolve this issue and will post further info as it becomes available. NS3 may become unresponsive for a brief period as we restart all DNS services on this machine.

Greetings, We are experiencing an issue with the DNS resolver on ns3.easydns.org this morning. This issue will not impact resolution. We are currently working with our network provider in London to resolve this issue. Thanks,

We are in the midst of changing the anycast address for ns1.easydns.com The new IP of ns1 will be 64.68.192.10 , we are in the process if switching the zone entry as well as updating the glue records for ns1.easydns.com We will leave the old IP operational for a couple of weeks. During this time […]