First they came for the file-sharing domains…
[easyDNS did not terminate wikileaks DNS, that was everyDNS. See this ]
(Background: as you may or may not be aware, earlier in the year the US Department of Homeland Security began seizing domain names of various filesharing websites. Suddenly the agency tasked with protecting the United States from further terrorist attacks was now seizing domain names to combat copyright infringement. Without further adieu ado, I bring you “First they came for the file-sharing websites….)
First, they came for the file-sharing websites, because they were infringing on copyright. (I didn’t care, because I didn’t share files).
Then, they came for the illegal offshore pharmacies, because they were facilitating the import of dangerous generic pharmaceuticals that massively undercut the name brand companies. (I didn’t care because I didn’t buy generic drugs)
These first choices may have seemed odd, because there were far worse things out there on the internet to go after. However, since nobody cared too much about the file-sharing sites and the illegal generic pharmacies, they figured it was safe to take things up a notch…. (more…)
Web Applications Developer
This is for our office here in Toronto, however we are not opposed to remote work for the right candidate. Such a person would have to have a proven track record of being able to work from a distance and achieve results.
Network issue – [resolved]
We recently experienced a network issue with one of our upstream providers at one of our co-location facilities. This issue was limited to just under an hour, during which time our sysAdmins worked with our upstream provider to determine the cause, and implement a fix. All affected systems are currently accessible and operating normally.
During this network issue, customers would have experienced slower than usual performance with the easyDNS interface, and some email delays. At no point was our primary DNS service affected.
We apologise for the inconvenience.
Email relay delays – [resolved]
First off, for more information about what greylisting is, please go to the following URL:
Today we experienced an issue with the greylisting service we have implemented upon our mailservers. Email that was being relayed to our mail forwarding servers was being deferred as the greylisting service was temporarily not accepting new email. As per the configuration for our greylisting, this led to the deferral, and thankfully not an outright rejection, of email, so no emails should have been lost (unless the sending mailserver gave up, which if it does within less than 24 hours, is a misconfiguration on the sending mailserver’s side).
Customers who noticed a lack of email during the day should expect to receive a backlog of email in the near future, if not already.
We apologise for any inconvenience this has caused, and shall be taking steps to ensure this does not happen again.
Warning: Unsolicited phone calls pretending to be "tech support"
We got this by way of William Porquet, reposted with permission as we think some of our users should be aware of this. It looks like an overseas boiler room operation is targeting users, the call reported below was received in Toronto, Canada:
The other day one of my older friends in Toronto received a mysterious
cold-call saying that “they” had detected problems with his computer
and that he should follow instructions to resolve them. He was
instructed to hit Windows Key + R and then type “www.onlinepccare.com”
into the box, which launched a web site. Then he was walked through
some (likely bogus) troubleshooting steps, which indicated some (also
likely bogus) errors. Then my friend explained to the caller that he
already had a tech support friend who keeps his computer in good
repair, and ask how much this “service” would cost. He was told by the
call-centre droid it would be $130, at which point my friend hung up
and called me.
So please treat any calls such as this with suspicion. Keep in mind when you are on a call with tech support, most of the time you initiate the call to your tech support, not the other way around. And when you are on a call, most likely you will actually know the name of the website they may be directing you to (although for the most part, you have probably already gone to the website yourself).
The larger issue is that first there was postal mail domain slammers to worry about, then email phishing attacks, now they’re working the voice phone lines.
Actually, now that I think of this, I am conducting market research on the viability of a telephone product that would filter out a call like this (among others), you would be helping matters if you took a short survey I posted on my personal blog about that.