Configuration before normal communication
DHCPv4 supplies configuration such as an IPv4 address, a lease duration, a router and DNS servers. A new client cannot assume that it already has an address suitable for normal unicast communication, so initial messages can use broadcast. Dynamic allocation reuses addresses across clients over time; an administrator can also reserve particular assignments. Receiving configuration is not proof that a web service is reachable. A valid address with an incorrect router, an unavailable DNS server, or an upstream routing failure can still leave applications unable to communicate.
Trace a new allocation
A common new-allocation sequence is DHCPDISCOVER, DHCPOFFER, DHCPREQUEST and DHCPACK. Suppose two servers offer different candidates. The client selects an offer and requests it; it does not automatically acquire every offered address. An offer of 192.0.2.40 is therefore different from the acknowledgment that completes the allocation procedure. Broadcast and unicast details depend on the client state and message fields. When inspecting a packet capture, correlate transaction identifiers and client identity rather than assuming that every nearby offer belongs to the same client.
Reason about renewal time
For an eight-hour lease with no explicitly supplied renewal timers, the usual default fractions place T1 at four hours and T2 at seven hours. The client first tries renewal with its original server, then enters rebinding when it needs to contact a broader set of servers. Lease expiration is not permission to keep using an old allocation indefinitely. A restarting client can also try to validate remembered configuration, so not every successful session contains a fresh four-message exchange. Record elapsed lease time when diagnosing periodic loss of connectivity.
Relays and trust boundaries
Routers normally do not forward local broadcasts as ordinary routed traffic. A relay can connect clients on one subnet to a server elsewhere, carrying information needed to choose an appropriate allocation pool. Seeing a Discover on the client link does not establish that the relay forwarded it or that the reply returned. The basic exchange also does not authenticate every configuration source. Unexpected router or DNS options can redirect traffic. Investigate allocation pools, relay configuration and network access controls, and avoid applying this DHCPv4 sequence unchanged to IPv6 configuration.