Servicios DHCP y DNS

Welcome to understanding two foundational services in any Linux network: DHCP and DNS.

These protocols work behind the scenes to make network communication smooth and user-friendly. One assigns network details, the other translates names.

DHCP stands for Dynamic Host Configuration Protocol. Its main job is to automatically assign IP addresses and other network settings (like subnet mask, default gateway, and DNS server addresses) to devices on a network.

• Saves time: No need to manually configure each device.
• Prevents errors: Avoids duplicate IP addresses.
• Flexible: Easily manage IP address pools.

When a device connects to a network, it uses a four-step process called DORA to get an IP address from a DHCP server:

• Discover: Client broadcasts a request for a DHCP server.
• Offer: DHCP server offers an available IP address.
• Request: Client accepts the offered IP.
• Acknowledge: Server confirms the lease and provides full configuration.

On Linux, a common DHCP server is provided by the isc-dhcp-server package (or dhcpd). The primary configuration file is typically located at /etc/dhcp/dhcpd.conf.

This file defines subnets, IP ranges, default gateways, and DNS servers that clients will receive.

Here's a simplified example of a dhcpd.conf entry for a local network. This tells the server what IPs to offer and what network details to provide.

DNS, or the Domain Name System, is like the internet's phonebook. It translates human-readable domain names (e.g., google.com) into machine-readable IP addresses (e.g., 142.250.191.46).

Without DNS, you'd have to remember complex IP addresses for every website!

When you type a domain name into your browser, a DNS query goes through several steps:

1. Your computer checks its local cache.
2. If not found, it asks a recursive DNS resolver (often provided by your ISP or a public one like 8.8.8.8).
3. The resolver queries root servers, then TLD servers (.com, .org), and finally the authoritative name server for the specific domain.
4. The authoritative server returns the IP address, which your computer then uses to connect.

On Linux, BIND (Berkeley Internet Name Domain) is the most common DNS server software. It's also known as named.

BIND manages zones, which are files containing records that map domain names to IP addresses (and vice versa) for specific domains.

Zone files are typically configured in /etc/bind/.

This is an example of a forward zone file for example.com. It defines how specific names within that domain map to IP addresses.

• @ represents the domain itself.
• NS records specify name servers.
• A records map hostnames to IPv4 addresses.

When things go wrong, these commands are your friends:

• systemctl status dhcpd / named: Check service status.
• journalctl -u dhcpd / named: View service logs.
• ip a: Verify your device's IP address (from DHCP).
• dig example.com: Query DNS for a domain.
• nslookup example.com: Another tool to query DNS.

You've learned about the distinct roles of DHCP and DNS. Let's test your understanding!

In this lesson, you gained insight into DHCP and DNS:

• DHCP automates IP address assignment, saving time and preventing errors.
• DNS translates human-readable domain names into machine-readable IP addresses.
• Both are critical services for any functional network, ensuring devices get online and can find each other by name.

Keep exploring these services to master network configuration!