- Install a Windows Server 2008 SP1 or SP2 DNS Server.
- From the Start menu, click "All Programs" -> Administrative Tools -> DNS.
- In the DNS Manager snap-in (Dnsmgmt.msc), right-click the node containing the name of the DNS server.
[-] <DNS Server Name> <- Right Click Here
[+] Global Logs
[+] Forward Lookup Zones
[+] Reverse Lookup Zones
- In the forwarders tab, toggle the setting for "Use root hints if no forwarders are available."
Enabling the checkbox for "use root hints if no forwarders are available" in the Windows Server 2008 DNS Manager snap-in, DNSMGMT.MSC, actually disables the use of root hints.
Unchecking the checkbox for “use root hints if no forwarders are available” in the Windows Server 2008 DNS Manager snap-in, DNSMGMT.MSC, actually enables the use of root hints.
A code defect in the Windows Server 2008 SP1 (RTM) and Service Pack 2 version of Dnsmgmt.msc causes the DNS service to use the opposite behavior than the Use root hints if no forwarders are available checkbox in the DNS Manager snap-in.
This problem does not exist in the Windows Server 2008 R2 version of Dnsmgmt.msc.
As a workaround, you can use the Windows Server 2008 version of the DNSCMD tool, which correctly displays and configures the root hint behavior. Otherwise use the opposite checkbox configuration to obtain the desired behavior. See the "More Information" section for the DNSCMD tool syntax.
The Use root hints if no forwarders are available checkbox in Windows Server 2008 DNS Manager is equivalent to the Do not use recursion for this domain in the Forwarders tab of the Windows Server 2003 DNS Manager snap-in.
Toggling the use root hints if no forwarders are available checkbox (or its Windows Server 2003 equivalent) modifies the following registry value:
Value Name: IsSlave
Value Path: HKLM\SYSTEM\CurrentControlSet\Services\DNS\Parameters
Value Type: REG_DWORD
Value Data: 0 | 1 (Default value: 0)
Not a slave. If the forwarder servers do not respond, the DNS server issues standard iterative queries to try to resolve the remote name.
Is a slave. If the forwarder servers do not respond, the DNS server terminates the search and sends a SERVER_FAILURE response to the query.
The DNS Server service and DNS Manager snap-in both read DNS registry entries only on startup. You can change entries while the DNS server is running by using the DNS console or DNSCMD tool. If you change entries by editing the registry or by using the DNSCMD tool, the changes are not effective until you restart the DNS Server service. Similarly, if DNS server registry keys are modified directly, restart the DNS Manager snap-in, Dnsmgmt.msc, so that it will reflect current configuration settings.
To view the status of the IsSlave setting in the registry using DNSCMD.EXE use the command:
To modify the value of the IsSlave setting using DNSCMD.EXE:
c:\>dnscmd /config /isslave 0
c:\>dnscmd /config /isslave 1
Sample output from "dnscmd /info" is shown below:
server name = dc1.contoso.com
version = <build #>
<truncated for brevity - scroll to bottom of DNSCMD output>
forward timeout = 5
slave = 0 <----Current value in registry for IsSlave
Command completed successfully.
Steps to reproduce.
Product Bug Number:
Problem is fixed in W2K8 R2 RTM via bug 213711
Problem is scheduled to be fixed in W2K8 SP3 as part of WINSE 239046
As of 2009.08.11, 1 customer has requested a QFE for WINSE 239046 from WINSE
111090778667602 - Heald College
Author ID (email alias): arrenc
Writer ID(email alias):
Tech Review ID (email alias):
Confirm Article has been Tech Reviewed: Yes/No
Confirm Article released for Publishing: Yes/No
Article ID: 2001154 - Last Review: Jan 15, 2013 - Revision: 1