Filtering does not work in the DNS Manager snap-in when you reverse lookup DNS zones to filter records in Windows Server 2008 R2

Article translations Article translations
Article ID: 2522461 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You open the DNS Manager snap-in on a computer that is running Windows Server 2008 R2.
  • You connect to a DNS server that has some reverse lookup zones in DNS Manager.
  • You perform the following actions to filter records in a reverse zone:
    1. You right-click the zone, select the View menu, and then click Filter.
    2. In the Filter dialog box, you select the Names starting with: or Names containing: options.
In this scenario, the filtering function does not work, and the matched records are not displayed.

For example, there are four records in the reverse lookup DNS zone:
192.168.1.1
192.168.1.2
192.168.2.1
192.168.2.2
If you filter these records by using the Name starting with: 192 condition, no record is displayed. However, the correct result displays all four records.

CAUSE

This issue occurs because DNS Manager incorrectly interprets reverse lookup DNS zone as forward DNS zone. Therefore, the filter function fails.

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 R2 or Windows Server 2008 R2 Service Pack 1 (SP1). Additionally, you must have DNS Server Tools installed.

For more information about how to obtain a Windows 7 or a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

If you close the DNS Manager snap-in before you install this hotfix, you do not have to restart the computer.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    Collapse this tableExpand this table
    VersionProductMilestoneService branch
    6.1.760 0.20xxxWindows Server 2008 R2RTMLDR
    6.1.760 1.21xxxWindows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Dnsmgmt.mscNot Applicable145,86710-Jun-200920:38Not Applicable
Dnsmgr.dll6.1.7600.209251,484,80016-Mar-201105:20x64
Dnsmgmt.mscNot Applicable145,86705-Nov-201001:55Not Applicable
Dnsmgr.dll6.1.7601.216831,484,28815-Mar-201105:12x64

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_185cae0328087dea52bc39a88c244523_31bf3856ad364e35_6.1.7600.20925_none_a8fac7d35cd9508a.manifest
File versionNot applicable
File size709
Date (UTC)16-Mar-2011
Time (UTC)15:56
PlatformNot applicable
File nameAmd64_d72001781813f6a5b9d8ca32ac3659b3_31bf3856ad364e35_6.1.7601.21683_none_a052570e788357ec.manifest
File versionNot applicable
File size709
Date (UTC)16-Mar-2011
Time (UTC)15:56
PlatformNot applicable
File nameAmd64_microsoft-windows-dns-server-snapin_31bf3856ad364e35_6.1.7600.20925_none_f332e3d43ded5619.manifest
File versionNot applicable
File size14,700
Date (UTC)16-Mar-2011
Time (UTC)06:04
PlatformNot applicable
File nameAmd64_microsoft-windows-dns-server-snapin_31bf3856ad364e35_6.1.7601.21683_none_f4d65ed83b4639d6.manifest
File versionNot applicable
File size14,700
Date (UTC)15-Mar-2011
Time (UTC)05:50
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,805
Date (UTC)16-Mar-2011
Time (UTC)15:56
PlatformNot applicable

Properties

Article ID: 2522461 - Last Review: April 13, 2011 - Revision: 1.0
APPLIES TO
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Foundation
  • Windows Server 2008 R2 Standard
  • Windows Web Server 2008 R2
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbdns kbexpertiseadvanced kbsurveynew KB2522461

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com