DOCUMENT:Q154555 10-AUG-2001 [winnt] TITLE :When to Enter Dotted vs Non-Dotted Names in DNS Manager PRODUCT :Microsoft Windows NT PROD/VER:4.0 OPER/SYS: KEYWORDS:kbnetwork ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Windows NT Server version 4.0 ------------------------------------------------------------------------------- SUMMARY ======= 1. The Domain names at which records are LOCATED (hostname for A, alias for CNAME, domain for SOA or NS, and so forth) must always be entered by creating the domains and entering a single part non-dotted DNS name. This policy is to avoid confusion when someone enters a dotted, non- Fully Qualified Domain Name (FQDN). Locate the domain in the tree and enter the name. 2. Domain names which are DATA in a record (NS nameserver, CNAME cannonical name, SOA primary name server and responsible party, MX mail server, and so forth) are always FQDNs. This is because these fields are not necessarily in the domain at all. This convention makes it simple; any domain name you type as RR data is considered an FQDN. Additional query words: prodnt ntdns ====================================================================== Keywords : kbnetwork Technology : kbWinNTsearch kbWinNT400search kbWinNTSsearch kbWinNTS400search kbWinNTS400 Version : 4.0 ============================================================================= THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Copyright Microsoft Corporation 2001.