You are currently offline, waiting for your internet to reconnect

Changes to DNS server behavior after you install the security update for DNS server

Support for Windows XP has ended

Microsoft ended support for Windows XP on April 8, 2014. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.


Post installation behavior on server computers after you install the DNS server security update

The purpose of this Knowledge Base article is to educate users about scenarios that are affected by an impending change to DNS server functionality. We have tried to make this document as generic as possible. Please read this document in its entirety and use it to understand if and how your enterprise environment may be affected by this update.

For more information about the DNS server security update, click the following article number to view the article in the Microsoft Knowledge Base:
961063MS09-008: Description of the security update for DNS server: March 10, 2009

Definitions table

Domain Name System (DNS)The Domain Name System is an Internet standard protocol that translates names to IP addresses and vice versa.
WPADWeb Proxy Auto-discovery Protocol
ISATAPIntra-Site Automatic Tunnel Addressing Protocol

An overview of the security issue

Internet Explorer and similar clients search for a proxy server by using the Web Proxy Auto-discovery Protocol (WPAD). Client computers look for the WPAD server by resolving the name WPAD and by using DNS. ISATAP (Intra-Site Automatic Tunnel Addressing Protocol) is an IPv6 transition technology. DNS Clients perform ISATAP discovery, which is similar to the method that is used for WPAD. Malicious registration of a WPAD or ISATAP entry inside a corporate network could allow for an attacker to configure a malicious proxy. There are workarounds for the security problem. For example, you can register a reserved name host entry in the DNS database. The administrator must register the host name without registering an IP address, thereby reserving the name host entry.

Changes to DNS after you apply the security update

The following changes to DNS will occur after you apply the DNS security update:
  • The security update automatically creates a block list that will be used by DNS. Every name query request is checked against the block list and a negative response is sent for the block listed name query.
  • The block list default depends on the data in the zones that the server is authoritative for when the update is run. If the zone data does not contain entries for WPAD or ISATAP, then the WPAD or ISATAP entries are populated in the block list.
  • If the DNS database already has any of these entries, then the WPAD or ISATAP entries are not populated in the block list.
  • The administrator can configure and edit the block list in the registry. DNS service has to be restarted for accepting the new block list.
  • For DNS, the block list applies to all zones that are hosted by the server. You cannot allow for WPAD and ISATAP queries in one zone but not another.
  • The block list is stored in the registry for each server. There is no replication of block list entries across multiple servers.

Frequently asked questions

  1. What happens if I upgrade my DNS server to LH server?
    Answer: A DNS server that uses valid entries of WPAD and ISATAP will continue to function as before.
  2. What is the location of the registry entry for the block list?
    Answer: The block list uses the GlobalQueryBlockList REG_MULTI_SZ entry in the following subkey:
  3. What if I delete the entries of the block list in the registry?
    Answer: All queries to WPAD and ISATAP will succeed after service restart.
  4. What happens if I delete the GlobalQueryBlockList registry key?
    Answer: When the service restarts, the key is added back, and the default block list values are repopulated. All the non-TXT WPAD and ISATAP queries will be blocked.
  5. What if I add an entry "contoso" to the block list in the registry?
    Answer: After you add the entry in the block list, all queries to contoso in any zone will fail as soon as the service is restarted.
  6. What happens if I already have an entry for contoso in the DNS database and I also add contoso in the blocked list?
    Answer: Queries to "" will fail.
  7. I have a WPAD server deployed in my network. Will I be affected?
    Answer: No. If you have WPAD deployed in a network, and you already have the name WPAD registered in DNS, then it will not be blocked. However, if you have WPAD in the network and it uses DHCP to distribute the wpad.dat file with nothing in DNS, then the DNS query for WPAD will be blocked.
  8. Can I use DNSCMD.exe to configure the block list?
    Answer: No. You can only change the block list in the registry.
  9. Would registration for blocked entries fail in the DNS server ?
    Answer: No. As part of the block list feature, registrations will succeed. Only queries for the blocked entries will fail.
  10. Are only Host (type A or AAAA) queries blocked by this feature?
    Answer: No, all kinds of queries for the names in the block list are blocked.
update security_patch security_update security bug flaw vulnerability malicious attacker exploit registry unauthenticated buffer overrun overflow specially-formed scope specially-crafted denial of service DoS TSE WinNT Win2000

Article ID: 968732 - Last Review: 11/30/2009 17:16:26 - Revision: 4.0

  • Microsoft Windows Server 2003 Service Pack 1
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows XP Professional x64 Edition
  • Microsoft Windows Server 2003 Service Pack 2
  • Microsoft Windows 2000 Service Pack 4
  • kbexpertiseinter kbsecurity kbsecvulnerability kbsurveynew KB968732