We have what looks like another DDoS in progress, we are still isolating the attack vector but things are stabilizing somewhat. More as it comes in. — On the subject of DDoS attacks, members can expect an all-member email around what we are doing behind the scenes to address these now, near constant DDoS attacks. […]
The Origin of the Gods
It’s been awhile since we posted under the “Who Uses easyDNS” section. This morning I was perusing the daily changes for our nameservers and noticed the following domain just transferred in: originofthegods.com. Having grown up on a steady diet of C.W Ceram, Greek mythology, The Golden Bough, et al I was pretty much hooked by […]
DNSResolvers open resolvers will be shut down.
We recently made the decision internally that our DNSResolvers.com had to cease being open resolvers. We were still trying to figure out the best way to transition to an authenticated model gracefully. However, tonight we were DDoS-ed against those open resolvers and while our core easyDNS authoritative DNS services were not impacted, our customer environment […]
This is what your registrar sees when your domain is seized under a sealed warrant.
We’ve commented before on the ramifications of US agencies operating via registry operators to seize domain names. What it effectively does is put all domain names registered under .com/.net/.org/.biz under the jurisdiction of US law, for better or for worse. Although I have never heard of the domain name that was seized (it looks like […]
Backup MX spool lifetime doubled to 10 days.
Given the flooding out in Alberta, there are many operations without power and experiencing unreachable servers and datacenter outages. As is normal for us during disasters like this, we are upping the backup MX spool lifetime here from five days to ten days, hopefully that’s enough time to get everything back online.
Post-mortem of the June 3-4th DDoS
As most of you are aware, we were DDoS-ed yesterday and experienced severe impact across our dns1, dns2 and dns3 anycast clouds. There was no identifiable target here on the system, rather, it appears as if our infrastructure was used in an attempt to DDoS somebody else, in other words, it was a DNS amplification […]
