10 years ago on this day, we removed the password block on easyDNS.com and sent out a couple of innocuous email announcements to the PHP and Mysql mailing lists announcing that we had developed a DNS management system using php and mysql and it was now open for business. We had three nameservers, 1 in […]
Blog
Is my ISP patched for the DNS cache poisoning bug?
We’re going to start an item here to try to keep track of the ISPs who are patched for the DNS cache poisoning bug. Most of our personal contacts are here in Canada so this list will likely be comprised largely of Canadian ISPs but as we get word on other big ones, we’ll try […]
easyDNS soft launches DNSresolvers.com
With the ramifications of the DNS cache poisoning bug beginning to sink in and the first exploit code being published today, we are anticipating an accelerating number of queries from our members about this and what they can do to ensure their own DNS caching resolvers are safe to use. We can tell you about […]
DNS cache poisoning exploit released
Hi There, There is a new DNS Cache poisoning disclosure that has been inadvertently leaked before it was scheduled to be released by Dan Kaminsky (IOActive). This is a very serious flaw in the DNS protocol that impacts caching resolvers, like the resolvers hosted at your service provider that help your workstation resolve IP addresses […]
RESOLVED: Duplicate emails being relayed…
The issue we were experiencing previously with duplicate emails has been resolved. Customers may receive yet one more copy of the duplicate emails as our queues clear out. Please contact Support if you continue to experience this issue: support@easydns.com We apologise for any inconvenience.
.ME Top Level Domain launch indicative of new TLD rollouts
We’ve gotten a few invitations to apply to be a .ME top-level domain registrar, to which we assigned no urgency after we took a straw poll internally and found that pretty well zero of our customers were asking for it. Today, Techcrunch reports that the .ME landrush, at least through one large operator, had degraded […]
