# DHCP

DHCP, the Dynamic Host Configuration Protocol, automatically supplies hosts with IP addressing and other network settings through renewable leases.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/dhcp

> DHCP reduces manual host configuration by distributing settings such as IP addresses, DNS servers, domain names, and lease durations. In cloud networks, engineers must distinguish configuration delivered to a guest operating system from provider-controlled resources that determine address ownership, routing, and security.

Practice exams covering DHCP: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty).

## 6 key aspects of DHCP

DHCP centralizes host network configuration, while lease timing, configuration scope, DNS dependencies, and separate routing controls determine its operational behavior.

1. **Lease-based configuration**: Clients obtain configuration for a defined lease period and renew it while operating. Plan configuration changes around renewal behavior rather than assuming every running host updates immediately.
2. **Options beyond IP addresses**: DHCP can distribute DNS servers, domain information, gateways, time servers, and other parameters. Verify which options the cloud platform supports and how the guest operating system applies them.
3. **Separate cloud address ownership**: A cloud control plane can assign an address to a network interface while DHCP delivers configuration to the guest. Dynamic guest configuration therefore does not imply that the private address changes on every renewal or restart.
4. **Explicit configuration scope**: Managed DHCP configuration follows virtual-network and administrative boundaries. In AWS, each VPC can have at most one associated DHCP option set, and corresponding resources must be created separately in other accounts or Regions.
5. **DNS configuration versus resolution**: DHCP identifies resolvers but does not implement DNS forwarding or guarantee that those resolvers can answer required names. Use reachable DNS infrastructure with explicit forwarding behavior for hybrid namespaces.
6. **Independent routing and security**: DHCP settings do not establish inter-VPC routes or grant application access. Validate routing, security controls, and custom resolver reachability separately.

## Cloud services for DHCP

Amazon VPC supplies managed DHCP configuration, and EC2 instances apply it through guest networking software. Route 53 Resolver handles DNS queries when workloads use the VPC-provided resolver, with forwarding rules and endpoints extending resolution to enterprise networks. AWS Directory Service introduces directory-specific DNS requirements that can be addressed through directory DNS servers or an appropriately designed forwarding architecture. Across accounts, Regions, and VPCs, deploy consistent DHCP settings while separately configuring resolver rules, endpoint reachability, routes, and security permissions. Validate the configuration actually received by clients after lease renewal rather than relying only on the VPC association.

- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: Amazon VPC provides managed DHCP infrastructure and DHCP option sets for supported host configuration. A VPC can have at most one associated option set, and the default association can be removed; these associations are separate from route tables and security controls.
- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: EC2 instances typically use DHCP clients to obtain network configuration. An interface's assigned private address and the guest's DHCP lease are distinct, so renewing a lease does not inherently change the assigned address.
- **[AWS Directory Service](https://blowstack.com/tools/cloud-services-hub/aws-directory-service)**: Directory-integrated workloads need DNS configuration that resolves their directory's records. For AWS Managed Microsoft AD, VPC DHCP options can advertise the directory DNS server addresses, provided clients have the required connectivity.

## DHCP exam questions

Real practice exam questions on DHCP, with the correct answer and its explanation.

### Question 1 (ANS-C01)

**Question:**

A company operates application VPCs in three AWS accounts across two AWS Regions. Each VPC is associated with a custom DHCP option set that specifies two corporate DNS server addresses. The company is replacing these servers with two new DNS servers that are already reachable from every VPC. Testing confirms that the new servers resolve all required names and that routing and security controls permit DNS traffic.

All application instances run Linux and obtain their resolver configuration through DHCP. Their next automatic DHCP renewals are more than 60 minutes away. The network team must make every instance use the new DNS servers within 15 minutes, without rebooting instances, changing their private IPv4 addresses, or configuring static resolver settings. AWS Systems Manager can run commands on every instance.

Which implementation meets these requirements?

**Correct answer:** Create a replacement DHCP option set in each account and Region, preserving the other required options and specifying the new DNS server addresses. Associate the replacement sets with the appropriate VPCs, and use Systems Manager to trigger DHCP lease renewal on the existing instances.

**Explanation:** DHCP option sets are immutable and scoped to an account and Region. Replacement sets must therefore be created in the relevant accounts and Regions and associated with the VPCs. Explicit DHCP renewal lets existing instances obtain the new resolver settings before their scheduled renewals. Renewal does not inherently change the primary private IPv4 address assigned to an instance's network interface.

## Practice DHCP in a full exam

Questions on DHCP in each practice exam, with every answer option and an explanation for each:

- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 1 question

## What is DHCP

Dynamic Host Configuration Protocol, or DHCP, lets a host obtain network configuration from a server instead of requiring an administrator to configure every setting manually. In a typical initial IPv4 exchange, the client broadcasts DHCPDISCOVER, receives DHCPOFFER, sends DHCPREQUEST, and receives DHCPACK. This sequence is commonly called DORA. DHCPv4 uses UDP server port 67 and client port 68. Clients subsequently renew their leases; not every renewal repeats the initial discovery sequence.

DHCP can deliver more than an IP address. Options can identify DNS servers, a domain name, a default gateway, time servers, and other supported parameters. Available options and client behavior vary by platform and operating system. DHCP does not perform DNS resolution itself: it tells clients which resolver to use. Similarly, receiving a gateway address does not create routes throughout a cloud network or authorize traffic through firewalls.

Cloud platforms commonly provide DHCP through their virtual networking infrastructure. The provider's control plane assigns an address to a virtual network interface, and DHCP communicates appropriate configuration to the guest. Consequently, a dynamically configured guest can have a stable private address. In Amazon EC2, the primary private IPv4 address remains associated with its network interface across instance stops and starts; renewing a DHCP lease does not inherently allocate a different address. Manually configuring an arbitrary address inside the guest does not assign that address to the cloud network interface.

In Amazon VPC, DHCP option sets control supported parameters such as domain names, DNS servers, and time servers. A VPC can have at most one associated DHCP option set, and its default association can be removed. One option set can be associated with multiple VPCs within the same account and Region. Option sets are immutable: to change their values, create a replacement and associate it with the required VPCs. Existing instances generally receive changed settings during lease renewal, so an association change is not necessarily reflected immediately in running guests.

For example, workloads that must resolve an enterprise directory domain might receive the addresses of reachable directory DNS servers through DHCP options. Those servers must also resolve or forward other required namespaces. Alternatively, workloads can retain the VPC-provided resolver and use Route 53 Resolver forwarding rules for selected enterprise domains. Supplying multiple DNS server addresses does not provide reliable domain-based query routing because clients differ in how they select and retry resolvers.

In multi-account, multi-Region, and multi-VPC architectures, configure DHCP independently of network connectivity. VPC peering and transit gateways do not merge DHCP configurations or forward client DHCP broadcasts between VPCs. Create and associate the intended option sets in each account and Region, then separately provide routes and security permissions to custom DNS or time servers. Changing DHCP options does not modify VPC route tables, security groups, or network ACLs. Traditional DHCP relay designs should not be assumed to work through cloud routed connectivity without explicit platform support.

The main trade-off is centralized consistency versus dependence on correct settings and client renewal behavior. An incorrect DNS option can disrupt applications even when IP connectivity remains healthy. Inspect the guest's effective address, lease, resolver configuration, and DNS responses before changing routes. Coordinate forced renewals carefully because operating-system commands can temporarily interrupt connectivity. On traditional networks, rogue DHCP servers are another concern because basic DHCP does not authenticate configuration sources. DHCPv6 is a separate protocol, and IPv6 networks may also use router advertisements and stateless address autoconfiguration; IPv4 DORA behavior does not describe every IPv6 deployment.
