Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Error resolving DNS records in top level domain (TLD) that has a purely numeric suffix


Author: Pavel Maslov MVP

View products that this article applies to.

Summary

Describes an issue in which you receive an error message when you connecting to server, establishing trust or joining domain with fully qualified domain name (FQDN) which resides in top level domain (TLD) that has a purely numeric suffix.

↑ Back to the top


Symptoms

When you try to connect to server by fully qualified domain name (FQDN) which resides in top level domain (TLD) that has a purely numeric suffix, connection is failed. If server is domain controller issue also affects establishing trusts and domain joins. When you try to PING server by FQDN you receive the following error message:

Ping request could not find host "FQDN of server". Please check the name and try again.

Note An example of a purely numeric suffix is "contoso.1234."

Connection to the server by IP or by NetBIOS name is succeeding.
When this issue occurs, all Domain Name System (DNS) records are correctly returned by NSLOOKUP. Therefore, DNS is fully functional and is not part of this issue.

↑ Back to the top


Cause

By default DNS client service rejects resolution of DNS records in top level domain (TLD) that has a purely numeric suffix.

↑ Back to the top


Resolution

To resolve this problem, add the ScreenBadTlds registry entry and restart DNS client service. Adding this registry entry prevents the DNS client service from performing the test to determine whether the top level domain is supported.

To add this registry entry and restart DNS client service, follow these steps.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

���� 322756 How to back up and restore the registry in Windows

�1. Click Start, and then click Run, type regedit in Open box, and then press ENTER.
�2. Locate and then click the following registry subkey:
���� HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters
�3. On the Edit menu, point to New, and then click DWORD Value.�
�4. Type ScreenBadTlds, and then press ENTER.
�5. Right-click ScreenBadTlds, and then click Modify.�
�6. In the Value data box, type 0, and then click OK.�
�7. Exit Registry Editor.
�8. Stop and then start the DNS client service. To do so:
�� �� a.� Click Start, and then click Run.
� ��� b.� In the Open box, type cmd, and then click OK.
�� �� c.� At the command prompt, type the following lines. Press ENTER after each line:
����� ������ net stop DNScache
������������ net start DNScache
����� d.� Type exit to quit Command Prompt.

↑ Back to the top


Properties

COMMUNITY SOLUTIONS CONTENT DISCLAIMER
MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.

↑ Back to the top


Community solutions content disclaimer

Microsoft corporation and/or its respective suppliers make no representations about the suitability, reliability, or accuracy of the information and related graphics contained herein. All such information and related graphics are provided "as is" without warranty of any kind. Microsoft and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information and related graphics, including all implied warranties and conditions of merchantability, fitness for a particular purpose, workmanlike effort, title and non-infringement. You specifically agree that in no event shall Microsoft and/or its suppliers be liable for any direct, indirect, punitive, incidental, special, consequential damages or any damages whatsoever including, without limitation, damages for loss of use, data or profits, arising out of or in any way connected with the use of or inability to use the information and related graphics contained herein, whether based on contract, tort, negligence, strict liability or otherwise, even if Microsoft or any of its suppliers has been advised of the possibility of damages.

↑ Back to the top


Keywords: kbpubmvp, kbpubtypecca, kbhowto, KB558120

↑ Back to the top

Article Info
Article ID : 558120
Revision : 1
Created on : 9/16/2008
Published on : 9/16/2008
Exists online : False
Views : 168