For example, this problem may occur when a Windows client computer that is running IPv6 tries to access a Web site. The Windows client will try to resolve the host name (for example, www.example.com) on behalf of applications that support both IPv6 and IPv4. To do this, the Windows client will query for both "AAAA" records and "A" records, unless the application specifies which protocol to use. If the DNS server replies with an authoritative response that returns NXDOMAIN or NAME_ERROR, Windows will return this response to applications, such as Internet Explorer. Because of this, the application will fail to resolve the host name and will be unable to access the site. Note that Windows clients will also cache this negative response. This prevents additional queries for this name from succeeding until the client cache is cleared.
Important In this example, if the DNS server that is used by the Windows IPv6 client caches negative responses, name resolution will also fail for other client computers when they use this same caching DNS server. This issue occurs regardless of the subsequent query type and regardless of whether the other client computers are running IPv6 or IPv4 only.
The DNS administrator of the site should contact the manufacturer of their DNS product for help resolving this issue. This may require an upgrade to the DNS server product or a change in the configuration of the DNS server or servers.
RFC 4047 Common Misbehavior Against DNS Queries for IPv6 Addresses
RFC 1034 Domain Names - Concepts and Facilities
RFC 2308 Negative Caching of DNS Queries (DNS NCACHE)
RFC 1035 Domain Names - Implementation and Specification
The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Article ID: 815768 - Last Review: Nov 20, 2013 - Revision: 1