NETWORK NAMING

63. The DHCP DNS option enables you to set the preferred primary and secondary DNS server for DHCP clients .

64. The DHCP WINS option enables you to set the preferred primary and secondary WINS server for DHCP clients.

65. The DHCP WINS node type option enables you to set the preferred NetBIOS name resolution method for DHCP clients.

66. The B-node (BROADCAST) WINS node type option (0x1) uses broadcasts only to resolve NetBIOS names .

67. The P-node (PEER-TO-PEER) WINS node type option (0x2) uses a NetBIOS name server/WINS server only to resolve NetBIOS names.

68. The M-node (MIXED) WINS node type option (0x4) uses broadcasts first; if the broadcast was unsuccessful , it then uses a WINS server to resolve NetBIOS names.

69. The H-node (HYBRID) WINS node type option (0x8) uses a WINS server first; if the WINS server was unsuccessful, it then uses broadcasts to resolve NetBIOS names.

70. Approximately 4MB of RAM is used when the DNS server is started without any zones. The DNS server consumes additional server memory for each zone or resource record added to the server.

71. Approximately 100 bytes of server memory are used for every resource record added to a server zone.

72. Caching-only DNS servers perform name resolution on behalf of clients and then cache the results; they are not configured to be authoritative for any DNS zones and, therefore, generate no DNS zone traffic.

73. Nonrecursive DNS servers that have had recursion disabled prevent the DNS server from using recursion to resolve names on behalf of clients. The server does not forward requests .

74. Forwarding-only DNS servers build up a name resolution cache relating names to IP addresses. This cache is used to resolve hostnames in an effort to manage DNS traffic between your network and the Internet.

75. Conditional forwarder DNS servers forward DNS queries according to the DNS domain name in the query.

76. Domain naming conventions for DNS names are outlined in RFC 1123. The allowed characters are all uppercase letters (A “Z), lowercase letters (a “z), numbers (0 “9), and the hyphen (-).

77. Standard DNS zone files, also known as traditional DNS zone files, are zone files stored as text files on the server's hard drive.

78. Active Directory “integrated DNS zones store DNS zone information in Active Directory. The zones are in multimaster formatting, meaning they can be updated on any server hosting the information.

79. Standard Primary DNS zones are read/write copies of the DNS zone. They can be directly updated only on the server storing this copy of the zone.

80. Standard Secondary DNS zones are read-only copies of the DNS zone and are updated only when zone transfers occur.

81. DNS stub zones are read-only copies of the DNS zone that contains a subset of the records associated with that zone. They also host information about the DNS servers that are authoritative for that domain.

82. Standard DNS zones cannot use a zone replication method based on Active Directory replication. Secure dynamic updates cannot be performed, either.

83. You can configure your DHCP servers to dynamically update DNS when the DHCP server configures a DHCP client with an IP address.

84. DNS clients running Windows 2000, Windows XP, and Windows Server 2003 can update DNS directly.

85. WINS forward-lookup resource records use a name query to WINS servers to provide name resolution of DNS queries for hostnames not found in a DNS zone.

86. WINS-R resource records in a reverse lookup zone provide name resolution for reverse queries not found in the DNS zone.

87. You should disable recursion on Internet- facing DNS servers that are authoritative for one or more internal DNS zones.

88. HOSTS files on systems have traditionally been used to resolve a fully qualified domain name (FQDN) to an IP address. These files are read from the top down, ignoring duplicate entries lower in the name list (because resolution stops after a match is made). To remain valid, they need to be manually updated on all systems.

89. LMHOST files on systems have traditionally been used to resolve NetBIOS names to an IP address. To remain valid, they need to be manually updated on all systems for consistency.

90. A single WINS server can service up to 10,000 clients for NetBIOS name resolution requests on most small to mid- sized networks.

91. Convergence time is the time it takes for a new entry in a WINS database to be replicated from the WINS server where changes were made to all other partner WINS servers.

92. WINS push partners replicate their changes with their push partners when a predefined change or update threshold has been reached on the originating WINS server.

93. WINS pull partners replicate their changes with their pull partners when a predefined time interval has lapsed on the WINS server, regardless of the number of changes made to the records database.

94. The four types of WINS traffic are Registration, Renewal, Query, and Release.

95. WINS burst mode handling is used to issue shortened temporary name registrations to clients when the WINS server is started with a clean database or during high traffic times.

96. WINS servers store a maximum of 25,000 name registrations by default and refresh queries in their queues before dropping additional queries.

97. DHCP servers must be authorized in Active Directory before they can assign IP addresses to clients.