IP Configuration and Addressing

IP Configuration and Addressing – CompTIA Server+ Guide

IP Configuration and Addressing is a foundational topic in server administration and a critical area tested on the CompTIA Server+ exam. Understanding how IP addresses are assigned, configured, and managed on servers is essential for maintaining network connectivity, security, and performance.

Why Is IP Configuration and Addressing Important?
Every server on a network requires a unique IP address to communicate with other devices. Misconfigured IP settings can lead to network outages, security vulnerabilities, duplicate address conflicts, and loss of access to critical services. As a server administrator, you must be able to properly configure, troubleshoot, and manage IP addressing to ensure reliable server operations. In enterprise environments, incorrect IP configuration can disrupt DNS resolution, prevent client connections, and cause cascading failures across dependent services.

What Is IP Configuration and Addressing?
IP configuration refers to the process of assigning and managing Internet Protocol (IP) addresses and related network settings on a server. Key components include:

• IP Address: A unique numerical identifier assigned to each device on a network. IPv4 addresses use a 32-bit format (e.g., 192.168.1.10), while IPv6 addresses use a 128-bit format (e.g., 2001:0db8:85a3::8a2e:0370:7334).

• Subnet Mask: Defines which portion of the IP address identifies the network and which identifies the host. For example, 255.255.255.0 (/24) means the first three octets identify the network.

• Default Gateway: The IP address of the router that forwards traffic from the local network to remote networks or the internet.

• DNS Servers: The addresses of Domain Name System servers that resolve hostnames to IP addresses.

• DHCP (Dynamic Host Configuration Protocol): A protocol that automatically assigns IP addresses and related configuration to devices on a network.

• Static IP Addressing: Manually assigning a fixed IP address to a server, which is the standard practice for servers that host services requiring consistent addresses.

IPv4 vs. IPv6
• IPv4: Uses 32-bit addresses, providing approximately 4.3 billion unique addresses. Addresses are written in dotted-decimal notation (e.g., 10.0.0.1). Subnetting and NAT (Network Address Translation) are commonly used to conserve address space.

• IPv6: Uses 128-bit addresses, providing a vastly larger address space. Addresses are written in hexadecimal separated by colons (e.g., fe80::1). IPv6 eliminates the need for NAT and includes features like auto-configuration (SLAAC – Stateless Address Autoconfiguration).

IP Address Classes (IPv4)
• Class A: 1.0.0.0 – 126.255.255.255 (large networks, default mask /8)
• Class B: 128.0.0.0 – 191.255.255.255 (medium networks, default mask /16)
• Class C: 192.0.0.0 – 223.255.255.255 (small networks, default mask /24)
• Class D: 224.0.0.0 – 239.255.255.255 (multicast)
• Class E: 240.0.0.0 – 255.255.255.255 (experimental/reserved)

Private IP Address Ranges (RFC 1918)
• 10.0.0.0 – 10.255.255.255 (Class A)
• 172.16.0.0 – 172.31.255.255 (Class B)
• 192.168.0.0 – 192.168.255.255 (Class C)
These ranges are not routable on the public internet and are used within private networks.

APIPA (Automatic Private IP Addressing)
When a device configured for DHCP cannot reach a DHCP server, it may self-assign an address in the 169.254.0.0/16 range. This is known as APIPA. If you see a server with a 169.254.x.x address, it indicates a DHCP failure.

How IP Configuration Works on Servers

Static Configuration:
Servers typically use static IP addresses to ensure services (web, email, DNS, database) remain accessible at a predictable address. Configuration involves manually setting the IP address, subnet mask, default gateway, and DNS server addresses through the operating system's network settings.

On Windows Server: Network adapter settings can be configured through the Network and Sharing Center, Server Manager, or via PowerShell commands such as New-NetIPAddress and Set-DnsClientServerAddress.

On Linux: Network configuration files vary by distribution (e.g., /etc/network/interfaces on Debian-based systems, /etc/sysconfig/network-scripts/ on RHEL-based systems, or using nmcli and ip commands). Netplan is used on newer Ubuntu versions.

Dynamic Configuration (DHCP):
While less common for servers, DHCP can be used with DHCP reservations to ensure a server always receives the same IP address from the DHCP server based on its MAC address. This combines the convenience of centralized management with the consistency of a static address.

Subnetting
Subnetting divides a larger network into smaller, more manageable subnetworks. Understanding CIDR (Classless Inter-Domain Routing) notation is important:
• /24 = 255.255.255.0 = 256 addresses (254 usable hosts)
• /25 = 255.255.255.128 = 128 addresses (126 usable hosts)
• /26 = 255.255.255.192 = 64 addresses (62 usable hosts)
• /27 = 255.255.255.224 = 32 addresses (30 usable hosts)
• /28 = 255.255.255.240 = 16 addresses (14 usable hosts)

The formula for usable hosts is: 2^(host bits) - 2 (subtracting the network and broadcast addresses).

NIC Teaming and Multiple IP Addresses
Servers often have multiple network interface cards (NICs). NIC teaming (bonding) combines multiple NICs for redundancy and increased bandwidth. A single NIC can also be configured with multiple IP addresses (IP aliasing) to host multiple services or virtual hosts.

VLAN Tagging
Servers may be configured with VLAN (Virtual LAN) tags to participate in multiple virtual networks over a single physical connection. This requires configuring the server's NIC to recognize and process VLAN-tagged traffic (802.1Q).

Common Troubleshooting Tools
• ipconfig (Windows) / ip addr or ifconfig (Linux): View current IP configuration
• ping: Test connectivity to another host
• tracert (Windows) / traceroute (Linux): Trace the route packets take to a destination
• nslookup / dig: Test DNS resolution
• netstat / ss: View active network connections and listening ports
• arp -a: View the ARP cache (IP-to-MAC address mappings)

Common IP Configuration Issues
• Duplicate IP addresses: Two devices assigned the same IP cause connectivity problems for both
• Incorrect subnet mask: Can prevent communication with other hosts on the same or different subnets
• Wrong default gateway: Server cannot reach hosts outside its local subnet
• Missing or incorrect DNS: Server cannot resolve hostnames, causing service failures
• APIPA address assigned: Indicates DHCP server is unreachable

---

Exam Tips: Answering Questions on IP Configuration and Addressing

1. Memorize private IP ranges: Know the RFC 1918 private address ranges (10.x.x.x, 172.16-31.x.x, 192.168.x.x). Exam questions frequently test whether you can identify private vs. public addresses.

2. Know APIPA: If a question describes a server that suddenly has a 169.254.x.x address, the answer almost always involves a DHCP server being unreachable.

3. Understand static vs. DHCP: Servers providing network services (DNS, DHCP, domain controllers, web servers) should use static IP addresses or DHCP reservations. Be prepared for scenario questions asking which is more appropriate.

4. Subnetting basics: You may be asked to calculate the number of usable hosts in a subnet, identify the correct subnet mask, or determine if two addresses are on the same network. Practice quick subnetting calculations.

5. Know your tools: Be familiar with which command-line tool is used for which purpose. Questions may describe a symptom and ask which tool you would use first to diagnose the issue.

6. IPv6 awareness: Understand the basic format of IPv6 addresses, the difference between link-local (fe80::) and global unicast addresses, and that IPv6 does not require NAT. You may see questions about dual-stack configurations (running both IPv4 and IPv6 simultaneously).

7. Read scenarios carefully: Many IP configuration questions are scenario-based. Pay close attention to details like the subnet mask, gateway address, and symptoms described. A single incorrect setting (wrong gateway, wrong mask) is often the root cause in troubleshooting scenarios.

8. Eliminate wrong answers: If a question asks about network connectivity issues, eliminate answers that involve unrelated components. Focus on the OSI Layer 3 (Network) elements: IP address, subnet mask, gateway, and routing.

9. DHCP reservations vs. static: Understand that DHCP reservations tie a specific IP to a MAC address on the DHCP server, while static addressing is configured directly on the server's NIC. Both achieve a consistent IP, but management differs.

10. NIC teaming considerations: Know that NIC teaming provides fault tolerance and load balancing. Questions may ask about the best approach to ensure server availability if a network link fails.

11. Document and verify: In best-practice questions, always prefer answers that include documenting IP assignments and verifying connectivity after making changes.

12. Loopback address: Remember that 127.0.0.1 (IPv4) and ::1 (IPv6) are loopback addresses used to test the local TCP/IP stack. If pinging 127.0.0.1 fails, the TCP/IP stack on the server itself is broken.