Tomorrow, we will be performing some maintenance, updating and upgrading the Caprica server. During that time, the Caprica users interface will not be accessible, and no changes will be able to be made to account settings of any sort (mail, zone records, etc…). This is a scheduled period at 12pm EST, which is expected to […]
Blog
Recent routing issues – update
The earlier difficulty with intermittent dns time-outs that affected some lookups has been traced to an issue with an upstream bandwidth provider, which caused delays on lookups which certain routes, resulting in the time-outs. For the time being, easyDNS has made some changes to ensure that this problem does not affect lookups against our users’ […]
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 […]
Saving trees the easy way!
We don’t want to sound like hippies here, but it’s sort of hard to miss the fact that there seem to be a lot fewer trees around than there were a while back, y’know? Whatever your take on global warming, we’ve all pretty much realized there’s been a bit too much of the chopping and […]
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 […]
