DNS & DHCP

A computer network can technically operate using manually configured addresses and direct IP communication, but managing a larger environment in that way quickly becomes difficult. DNS and DHCP provide important services that make network administration more scalable and practical.

The Domain Name System, or DNS, provides a hierarchical naming system that allows users and applications to work with names rather than remembering numerical IP addresses. DHCP, or Dynamic Host Configuration Protocol, provides clients with IP addresses and other network configuration automatically.

Because DNS and DHCP sit between clients, infrastructure, and applications, they frequently appear in computer networking assignments, network administration coursework, infrastructure projects, troubleshooting exercises, and network design work.

1. An application or operating system needs to resolve a domain name.
2. The client checks relevant local information, such as DNS cache or local configuration, depending on the operating environment.
3. The client sends a DNS query to its configured recursive resolver.
4. If the resolver has a valid cached answer, it can return that answer without performing the complete lookup process again.
5. If the answer is not cached, the resolver can query the DNS hierarchy to locate the appropriate authoritative information.
6. The authoritative DNS server returns the relevant record or an appropriate response.
7. The resolver can cache the response according to its TTL and return the result to the client.

This process explains why DNS can often appear instantaneous to an end user even though the resolver may have performed significant work behind the scenes. Caching allows previously obtained information to be reused until the relevant TTL permits or requires another lookup.

• Creating and maintaining DNS zones
• Managing authoritative name servers
• Adding and modifying DNS records
• Configuring forward lookup zones
• Configuring reverse lookup zones
• Managing TTL values
• Understanding DNS delegation
• Monitoring DNS availability
• Testing DNS resolution
• Investigating incorrect DNS responses
• Managing DNS caching
• Considering DNS security

DNS administration assignments may ask students to design zones, create records, explain delegation, configure a DNS server, analyse lookup behaviour, or troubleshoot a domain that is not resolving as expected.

The DORA process provides a useful conceptual model for understanding how a client can obtain an address dynamically. Real DHCP environments may involve additional message exchanges and renewal behaviour, particularly after a client already has an active lease.

• Creating DHCP scopes
• Defining address pools
• Configuring excluded addresses
• Setting lease durations
• Configuring default gateways
• Providing DNS server information
• Creating DHCP reservations
• Managing DHCP options
• Using DHCP relay agents
• Monitoring active leases
• Investigating address conflicts
• Troubleshooting clients that cannot obtain addresses

DHCP project work may involve designing an address allocation strategy, configuring multiple scopes, assigning gateways and DNS servers, creating reservations, or explaining how clients in different subnets can reach a centralized DHCP server through relay agents.

DNS security involves more than simply ensuring that records resolve correctly. Administrators also need to consider who can modify records, how DNS servers are exposed, how recursive resolution is controlled, and how DNS responses can be protected from manipulation.

• DNSSEC and DNS data authenticity
• Protection against DNS cache poisoning
• Secure DNS administration
• Access control for DNS management
• Monitoring DNS infrastructure
• Protecting authoritative DNS services
• Understanding recursive-resolver exposure
• Preventing unauthorized DNS changes
• Logging and auditing DNS activity
• Considering encrypted DNS technologies where appropriate

DNSSEC is one important technology in this area. It provides mechanisms for validating the authenticity and integrity of DNS data, helping address certain classes of DNS manipulation.

1. Check whether the client has received an IP address at all.
2. Verify that the DHCP server is available and reachable.
3. Check whether the DHCP scope has available addresses.
4. Verify VLAN and Layer 2 connectivity between the client and the DHCP relay or server.
5. Check DHCP relay configuration when the server is located on another network.
6. Verify subnet masks and default-gateway information supplied by DHCP.
7. Check the DNS server information being supplied through DHCP options.
8. Look for duplicate-address or conflicting configuration problems.
9. Check lease status and expiration information.
10. Review DHCP server logs when clients repeatedly fail to obtain valid configuration.

DHCP troubleshooting is closely connected to other networking concepts. VLAN configuration, routing, broadcast behaviour, DHCP relay, IP addressing, and firewall policies can all influence whether a client successfully receives its configuration.

• Maintain a clear and documented IP addressing plan.
• Use consistent DNS naming conventions.
• Keep DNS records accurate and remove obsolete records when appropriate.
• Use appropriate TTL values for the operational requirements of the environment.
• Document DHCP scopes, exclusions, reservations, and options.
• Avoid overlapping DHCP address pools.
• Use DHCP reservations where predictable addressing is useful without abandoning centralized configuration.
• Separate authoritative DNS responsibilities from recursive resolution where the architecture requires it.
• Monitor DNS and DHCP services for availability and configuration problems.
• Use command-line diagnostic tools to verify actual network behaviour.
• Protect administrative access to DNS and DHCP infrastructure.
• Document changes so that future troubleshooting does not depend on assumptions.

• DNS provides a hierarchical naming system used for locating hosts and services.
• DNS resolvers obtain answers through caching or communication with other DNS servers.
• Authoritative DNS servers provide authoritative information for the zones they serve.
• DNS records such as A, AAAA, CNAME, MX, NS, PTR, TXT, and SOA serve different purposes.
• DNS caching and TTL values affect how quickly previously obtained information is reused.
• DHCP automatically provides clients with IP configuration and other network parameters.
• DHCP scopes define address allocation ranges.
• DHCP reservations can provide predictable addresses while retaining centralized configuration.
• DHCP relay agents allow clients and servers on different networks to communicate through DHCP.
• nslookup, dig, host, ipconfig, and other tools can provide valuable evidence during troubleshooting.
• DNS and DHCP commonly work together as fundamental network infrastructure services.