---
title: "DNSResolvers open resolvers will be shut down."
type: "post"
post_id: "3125"
slug: "dnsresolvers-open-resolvers-will-be-shut-down"
canonical: "https://easydns.com/blog/2013/06/27/dnsresolvers-open-resolvers-will-be-shut-down/"
markdown_url: "https://easydns.com/blog/2013/06/27/dnsresolvers-open-resolvers-will-be-shut-down.md"
json_url: "https://easydns.com/blog/2013/06/27/dnsresolvers-open-resolvers-will-be-shut-down.json"
txt_url: "https://easydns.com/blog/2013/06/27/dnsresolvers-open-resolvers-will-be-shut-down.txt"
published: "2013-06-28T02:54:56+00:00"
modified: "2024-11-13T17:23:27+00:00"
author: "Mark E. Jeftovic"
categories:
  - "What's New"
tags:
  - "DDoS"
  - "DNSresolvers"
  - "google's public DNS"
  - "no good deed..."
  - "opendns"
site_name: "easyDNS"
publisher: ""
language: "en-US"
generator: "easyPress Markdown"
generator_version: "1.0.3"
---
We recently made the decision internally that our [DNSResolvers.com](http://www.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 was slightly degraded and URL forwarding and mail forwarding experienced slowdowns. So that settles it: the DNSResolvers.com publicly accessible resolvers are going away sooner than later.

We may offer authenticated resolver services for our customers in the future, but until we get there if you are using DNSresolvers now, you should switch away to another option ***immediately.***

Two spring to mind:[ OpenDNS](http://www.opendns.com) and [Goo](https://developers.google.com/speed/public-dns/docs/using)[gle’s Public DNS.](https://developers.google.com/speed/public-dns/docs/using)

DNSResolvers was free, it was not our core business, and we now exist in online environment where nobody should be running open public resolvers unless they are devoting ample resources toward making sure they aren’t part of the DNS amplification problem. The moment it interferes with our core business (like it just did) is the time to jettison it.

Nobody wants their paid services degraded by a DDoS against some free service that gets rampantly abused and shouldn’t be wide open anyway. We’re sorry to have to pull the plug on it and we would appreciate your understanding.

P.S if you don’t know what resolvers you are using, we have a tool for detecting that at [MyResolver.com. ](http://myresolver.com)If it says *205.210.42.205* or *64.68.200.200* then you are currently using DNSResolvers.com and you need to switch away.