Between 2:08pm EST and 2:18pm EST, there was a connectivity issue with two nodes within the “dns2.easydns.net” Anycast cluster. This was traced back to a minor internal issue with our upstream provider, which they quickly addressed. During this time, the two nodes would have been inaccessible, yet the other nodes within the Anycast cluster would […]
status
[RESOLVED]: cache2.dnsresolvers.com currently unresponsive
RESOLVED: We have found and resolved the issue with the cache2.dnsresolvers.com cache2.dnsresolvers.com is currently unresponsive. DNSresolvers.com is our public service recursive DNS service, it’s unicast but does no NXDOMAIN interception or typo “correction”. cache1.dnsresolvers.com is functioning as expected. The systems group is investigating. All core easyDNS systems (DNS resolution, forwarding, email, etc) are unaffected […]
[RESOLVED]: Mail Forwarding to Verizon
Our mail forwarding system (not to be confused with our mailout system) is experiencing delays with relaying mail to @verizon.net . We have contacted Verizon and they have advised the issue to be cleared, however they have not provided a time line as to when mail will flow without restriction. We will continue to monitor […]
[RESOLVED] Mailout Slowness
Our mailout system is experiencing slower than usual mail delivery times . We have isolated and corrected the issue causing the slowness and the mail queue is slowly – but surely – being processed. [ UPDATE – 2012-03-26 @ 3:39pm EST ] All mail has been dequeued at this point, and we’re back to normal […]
Small DNS flood to our nameservers
Yesterday afternoon we were alerted of a domain upon our system that was known within DNS provider circles for excessive traffic, and attempted to have this issue dealt with before it became a problem. Unfortunately, while the domain was delegated to us for only a short time, we did see some spikes in traffic during […]
[Resolved] Sporadic connectivity to dns2.easydns.net
We have had reports of sporadic DNS connectivity to “dns2.easydns.net” from various customers. We have confirmed this and alerted our upstream provider. They believe this is a routing issue, and are escalating this on their end with their networking team. We apologise for the inconvenience, and hope to have this resolved as soon as possible. […]
