Some customers from Europe and Asia have brought to our attention that they are experiencing sporadic network issues when attempting to perform DNS queries against “ns1.easydns.com” and “dns1.easydns.com”. We have been able to replicate the issue, and are working with our upstream provider to determine the cause and implement a fix. We apologise for the […]
Connectivity issue with some servers
We are currently experiencing an issue at one of our co-location facilities, resulting in some servers being inaccessible. The easyDNS interfaces (both legacy and current) are not affected, nor are our nameservers. Our upstream provider is investigating the issue, and hopes to have it resolved as soon as possible. We apologise for the inconvenience. [UPDATE […]
Recent routing issues
We recently experienced a routing issue which affected one of our primary nameservers and two legacy nameservers for some of our customers: ns1.easydns.com remote1.easydns.com ns3.easydns.org During this time, DNS queries to the nameservers listed above may have resulted in timeouts. This appears to have affected customers that have their internet connectivity peered through Level3. This […]
Upcoming Maintenance
On the evening of Monday MArch 28th we will be performing network maintenance at one of our Toronto area data centres. The purpose of this maintenance is to switch our network providers. Everything will be prewired and ready to go however we do expect a couple of small blips , none of which we expect […]
Recent "dns3.easydns.org" issues…
We recently experienced an issue with one of the nodes that makes up the “dns3.easydns.org” Anycast cluster, which resulted in resolution errors for “easydns.com”, and some other domains. The node in question is located in London, England, so this would have mostly affected customers located in the United Kingdom. We have since removed this node […]
ns1/dns1 update
With the help of our provider we have terminated all BGP sessions originating from our machine in Tokyo. The result of this is that no queries should be directed there. This will remain off until such time that we can login and assess what has happened to the machine. As always thank you for your […]
