I don't have the strongest background in computer security, but yesterday one of my company servers was shut down by our host.

It's a server assigned a public IP where I host several web-service applications including websites and APIs. I was told that my server "is running an open dns resolver which is being used to relay the denial of service attack to an external entity."

What does this mean? How does this attack work? And how can I protect my system from being abused like this?

In my specific case, the server in question is on Windows Server 2012, and it is serving DNS for an Active Directory domain.

  • If you let us know which DNS server you use, someone can probably tell you precisely which configuration you need to set, and in which fashion. Without that information, I simply guessed BIND and all private IP address spaces, because BIND is the most common DNS server and the private address spaces are safe. You'd probably want to allow recursive requests from your external address block(s) as well, if applicable. Feb 5, 2014 at 19:43
  • @HopelessN00b Thank you, your answer was quite useful. I'm not using BIND (my host also assumed I was and provided me with some commands to run); I have a DNS server set up as a role in IIS. It's interesting, I did not manually configure a DNS server and I'm not sure that I quite understand why I even need this. What breaks if it gets disabled?
    – JSideris
    Feb 5, 2014 at 20:00
  • Uh, don't disable DNS in a Windows environment. It's likely you'll break Active Directory. Let me know what version of Windows Server, and I can (probably) edit in some screenshots to show you how to secure a Windows DNS box. Feb 5, 2014 at 20:02
  • Alright. I actually just set up active directory this weekend. It's windows server 2012 standard.
    – JSideris
    Feb 5, 2014 at 20:05

1 Answer 1


An "open DNS resolver" is a DNS server that's willing to resolve recursive DNS lookups for anyone on the internet. It's much like an open SMTP relay, in that the simple lack of authentication allows malicious 3rd parties to propagate their payloads using your unsecured equipment. With open SMTP relays, the problem is that they forward spam. With open DNS resolvers, the problem is that they allow a denial of service attack known as a DNS Amplification Attack.

The way this attack works is pretty simple - because your server will resolve recursive DNS queries from anyone, an attacker can cause it to participate in a DDoS by sending your server a recursive DNS query that will return a large amount of data, much larger than the original DNS request packet. By spoofing (faking) their IP address, they'll direct this extra traffic to their victim's computers instead of their own, and of course, they'll make as many requests as fast as they can to your server, and any other open DNS resolvers they can find. In this manner, someone with a relatively small pipe can "amplify" a denial of service attack by using all the bandwidth on their pipe to direct a much larger volume of traffic at their victims.

ArsTechnica did a decent article on the recent DNS Amplification DDoS attack against Spamhaus, and is worth a quick read to get the basics (and a good visual of the amplification).

The simplest way to protect your system from being abused like this is to limit the addresses your server will perform recursive lookups for to your local subnets. (The specifics of which depend on which DNS server you're using, of course).

For example, if I were using BIND 9, and wanted to simply prevent DNS recursion from outside addresses, I would use the following code in my config:

options {
    directory "/var/named/master";
    allow-recursion {;;;; };

That line of code tells my BIND server to only process recursive DNS requests for the local loopback address (which I guess I could/should set to the local loopback block, the whole /8) and the 3 Private IPv4 address spaces.

For Windows Server 2012, which you say you're using, you have the options below.

1. Separate your DNS server from your IIS server.

  • At least in a perfect world, there's no reason you need to be running DNS on the same box as IIS.
    • Put DNS on an internal box that isn't NATed, so the outside world can't get at it, and let IIS reside on the external-facing box that the rest of the world can get at. You can use dual-homing or firewall rules to selectively allow access to your DNS server from your IIS server.

2. Block external DNS requests with a firewall, such as the built in Windows firewall.

  • To my surprise, Windows DNS does not allow you to restrict the addresses to which recursive DNS requests are honored, so this actually the recommended method by Microsoft.
  • enter image description here
    • Select the DNS rules (TCP and UDP), go to the Remote IP address section and add the subnets in use on your LAN, as well as any public-facing IP addresses of servers that need access to Active Directory. As with the BIND example, IPv4 private address spaces are and

3. Disable recursion.

  • I'm honestly not sure what effect this will have on your environment, since you haven't really stated how DNS and AD are configured in your environment, and accordingly, it's the last option.
  • enter image description here
    1. Open DNS Manager.
    2. In the console tree, right-click the applicable DNS server, then click Properties.
    3. Where?
    4. DNS/applicable DNS server
    5. Click the Advanced tab.
    6. In Server options, select the Disable recursion check box, and then click OK.
      • Since we have a multi-forest environment, and use conditional forwarders for that to work, I'm not going to check that box. Might be something for you to consider as well.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.