-
TCP/IP is automatically installed with Windows Server 2003 when a network adapter is detected .
-
The default configuration for a computer running Windows Server 2003 is to automatically obtain an IP address from a DHCP server.
-
IP addresses can be assigned either dynamically using a DHCP server or statically (manually).
-
Clients use automatic private IP addressing if they are enabled for DHCP but no DHCP server is available. DHCP clients using APIPA assign themselves an IP address in the range of 169.254.0.1 to 169.254.255.254.
-
Clients using APIPA are limited to communicating on the local subnet because only an IP address and subnet mask are configured.
-
A computer can be configured with multiple gateways. The gateway with the lowest metric is preferred.
-
Windows Server 2003 supports WINS to remain backward compatible with legacy clients.
-
LMHOSTS is a static text file that maps NetBIOS names to IP addresses.
-
TCP/IP filtering is used to filter network traffic based on TCP/UDP ports and IP protocols.
-
The Dynamic Host Configuration Protocol (DHCP) is used to dynamically assign IP addresses and other parameters to DHCP clients.
-
The DHCP lease process includes the following four phases: Discover, Offer, Request, Acknowledge (remember "DORA").
-
A DHCP server must be configured with a static IP address.
-
Every DHCP server requires a scope. For fault tolerance, use the 80/20 rule with multiple DHCP servers. Scopes must not overlap because DHCP servers do not share scope information.
-
Superscopes enable a DHCP server to assign IP addresses from multiple scopes to DHCP clients on one physical network. Multicast scopes enable messages to be sent to a group of computers.
-
DHCP can be integrated with DNS. DHCP can update the resource records on behalf of DHCP clients and clients that do not support dynamic updates.
-
Dynamic update registration credentials specify the user account under which a DHCP server performs updates to the DNS database.
-
A DHCP server must be authorized within Active Directory before it can lease IP addresses to DHCP clients. You must be a member of the Enterprise Admins group to authorize a DHCP server.
-
Optional parameters can be configured at the server, scope, class, and client levels. Settings are applied in the following order: server, scope, class, and client. Settings configured at the client level override those configured at any of the other three levels.
-
DNS is a distributed database that maps domain names to IP addresses.
-
Recursive queries require the DNS server to respond with the IP address of the request or an error message that the requested name does not exist.
-
With iterative queries, the DNS server uses zone information and its cache to return the best possible answer.
-
Zone files contain configuration information for the zone as well as the resource records.
-
The process of replicating a zone file to a secondary server is referred to as a zone transfer.
-
Pre-Windows 2000 implementations of DNS supported a full zone transfer (AXFR) only, in which the entire zone file is replicated to the secondary server. This type of zone transfer is supported by most implementations of DNS.
-
Windows 2000 and Windows Server 2003 support incremental zone transfers where only the changes are replicated instead of the entire zone file.
-
DNS can be installed during the installation of Windows Server 2003, using the Add or Remove Programs applet, or when promoting a server to a domain controller.
-
A DNS zone is a portion of the DNS database that is administered as a single unit.
-
Caching-only servers do not maintain any zone information. They resolve names on behalf of clients and cache the results. Caching-only servers are useful when network traffic needs to be reduced.
-
Primary DNS servers maintain the working copy of the zone database file, whereas the secondary DNS servers maintain a replica.
-
BIND 4.9.6 supports SRV records. BIND 8.1.3 supports dynamic updates.
-
A forward lookup zone maps hostnames to IP addresses. A reverse lookup zone maps IP addresses to hostnames.
-
Three zone types are supported: standard primary, standard secondary, and stub. Primary and stub zones can be converted to Active Directory-integrated zones.
-
Stub zones maintain a list of authoritative name server for a zone.
-
A zone file is replicated from a master name server to a secondary DNS server. A master name server can be a primary DNS server or another secondary DNS server.
-
Host Address (A) records map DNS names to IP addresses.
-
The Serial Number lists the number used to determine whether the zone file has changed. Each time a change is made, this number is incremented by 1. You can force a zone transfer by manually increasing this number.
-
The Refresh Interval determines how often the secondary server polls the primary server for updates.
-
The Time-To-Live (TTL) specifies how long DNS servers are allowed to store a record from the zone in their cache before it expires .
-
A forwarder is a DNS server that receives DNS queries that cannot be resolved locally and forwards them to external DNS servers.
-
When configuring zones, use the Name Servers tab and the Zone Transfers tab to limit which servers can receive DNS updates and transfers.
-
DNS servers that store information within Active Directory poll Active Directory at 15-minute intervals to check for updates.
-
DNS supports dynamic updates so that clients can dynamically register and update their own resource records. Secure updates can also be configured so that only those clients with permission to use the zone file can perform updates.
-
When configuring dynamic updates, the zone must be standard primary (information is stored locally in files) or Active Directory-integrated (information is stored on all DCs). Also, to use secure updates, the zone must be Active Directory-integrated. This feature is not supported by standard primary zones.
-
Using delegation, administrators can divide a namespace among multiple zones.
-
The DNS service can be monitored using various tools, including System Monitor, Event Viewer, and Replication Monitor.
