HOW TO USE DNS CLIENT SETTINGS IN COMPUTER

DNS configuration involves the following tasks when configuring TCP/IP properties for each computer: For example: Setting a DNS computer or host name for each computer., in the fully qualified domain name (FQDN) Samirreports.blogspot.com., the DNS computer name is the leftmost label samirreports. Setting a primary DNS suffix for the computer, which is placed after the computer or host name to form the FQDN. Setting a list of DNS servers for clients to use when resolving DNS names, such as a preferred DNS server.
Setting computer names
When setting computer names for DNS, it is useful to think of the name as the leftmost portion of a fully qualified domain name (FQDN).Example: in samirreports.blogspot.com.. samirreports is the computer name. ITS can configure all Windows DNS clients with a computer name based on any of the standard supported characters defined in Request for Comments (RFC) 1123, "Requirements for Internet Hosts -- Application and Support. If you are supporting both NetBIOS and DNS namespaces on your network, it can use a different computer name within each namespace. It is recommended that wherever possible, however, you try to use computer names that are 15 char requirements outlined above acters or less and that you follow the RFC 1123 naming. By default, the leftmost label in the FQDN for clients equals the NetBIOS computer name, unless this label is 16 or more characters, which is the maximum for NetBIOS names. When the computer name exceeds the maximum length for NetBIOS, the NetBIOS computer name is truncated based on the full label that is specified.
Before configuring computers with varying DNS and NetBIOS name.
consider the following implications and their related issues for your deployment.
If you have an investment in using NetBIOS names to support legacy networking technology, it is recommended that you revise NetBIOS computer names used on your network to prepare for migration to a standard DNS-only environment. This prepares your network well for long-term growth and interoperability with future naming requirements. For example, if you use the same computer name for both
NetBIOS and DNS resolution,
Consider converting any special characters such as the underscore (_) in your current NetBIOS names that do not comply with DNS naming standards. While these characters are permitted in NetBIOS names, they are more often incompatible with traditional DNS host naming requirements and most existing DNS resolver client software.
Notes
Although the use of the underscore (_) in DNS host names or in host resource records has been traditionally prohibited by DNS standards, the use of underscores in service-related names--such as those used for service locator (SRV) resource records--has been proposed to avoid naming collisions in the Internet DNS namespace. For more information.
if(typeof(IsPrinterFriendly) != "undefined")
{
var l = "/WindowsServer/en/library/60601f25-a8b3-4316-851f-8e0cc99673ec1033.mspx";
var nl;
var c = l.charAt(0);
var o = document.getElementById("ELC");
switch (c){
case "/":
nl=(" [http://" + document.domain + l + "]");
break
case "#":
nl=("");
break
default:
nl=" [" + l + "]"
}
if(o != null) o.innerHTML = nl;
}
.

In addition to DNS standard naming conventions, Windows Server 2003 DNS supports the use of extended ASCII and Unicode characters. However, since most resolver software written for other platforms (such as UNIX) is based on the Internet DNS standards, this enhanced character support can be used only in private networks with computers running Windows 2000 or Windows Server 2003 DNS.
The initial setup of DNS and TCP/IP displays a warning to suggest a standard DNS name if a nonstandard DNS name is entered.
By default, computers and servers use DNS to resolve any name that is greater than 15 characters in length. If the name is less than or equal to 15characters, then both NetBIOS and DNS name resolution can be attempted and used to resolve the name.

Setting domain names
The domain name is used with the client computer name to form the fully qualified domain name (FQDN), known also as the full computer name. In general, the DNS domain name is the remainder of the FQDN that is not used as the unique host name for the computer.
For example, the DNS domain name used for a client computer could be the following: If the FQDN, or Full computer name, is
samirreports.blogspot.com.
DNS domain names have two variations--a DNS name and a NetBIOS name. The full computer name (a fully qualified DNS name) is used during querying and location of named resources on your network. For earlier version clients, the NetBIOS name is used to locate various types of NetBIOS services that are shared on your network.
Example that shows the need for both NetBIOS and DNS names is the Net Logon service. In Windows Server 2003 DNS, the Net Logon service on a domain controller registers its service (SRV) resource records on a DNS server. For Windows NT Server 4.0 and earlier versions, domain controllers register a DomainName entry in WINS to perform the same registration and to advertise their availability for providing authentication service to the network.
When a client computer is started on the network, it uses the DNS resolver to query a DNS server for SRV records for its configured domain name. This query is used to locate domain controllers and provide logon authentication for accessing network resources. A client or a domain controller on the network optionally uses the NetBIOS resolver service to query WINS servers, attempting to locate DomainName [1C] entries to complete the logon process.

Your DNS domain names should follow the same standards and recommended practices that apply to DNS computer naming described in the previous section. In general, acceptable naming conventions for domain names include the use of letters A through Z, numerals 0 through 9, and the hyphen (-). The use of the period (.) in a domain name is always used to separate the discrete parts of a domain name, commonly known as labels. Each label corresponds to an additional level defined in the DNS namespace tree.
For most computers, the primary DNS suffix configured for the computer can be the same as its Active Directory domain name, although the two values can also be different.
By default, the primary DNS suffix portion of a computer's FQDN must be the same as the name of the Active Directory domain where the computer is located. To allow different primary DNS suffixes, a domain administrator may create a restricted list of allowed.
suffixes by creating the msDS-AllowedDNSSuffixes attribute in the domain object container. This attribute is created and managed by the domain administrator using Active Directory Service Interfaces or the Lightweight Directory Access Protocol (LDAP).

For computers running Windows XP, the DNS server list is used by clients only to resolve DNS names. When clients send dynamic updates, such as when they change their DNS domain name or a configured IP address, they might contact these servers or other DNS servers as needed to update their DNS resource records.
if(typeof(IsPrinterFriendly) != "undefined")
{
var l = "/WindowsServer/en/library/e760737e-9e55-458d-b5ed-a1ae9e04819e1033.mspx";
var nl;
var c = l.charAt(0);
var o = document.getElementById("EWE");
switch (c){
case "/":
nl=(" [http://" + document.domain + l + "]");
break
case "#":
nl=("");
break
default:
nl=" [" + l + "]"
}
if(o != null) o.innerHTML = nl;
}
.
By default, the DNS client on Windows XP does not attempt dynamic update over a Remote Access Service (RAS) or virtual private network connection. To modify this configuration, you can modify the advanced TCP/IP settings of the particular network connection or modify the registry.