Verify DHCP option 119 support on the client before changing pfSense search domains

A configured search list is ineffective when the client does not request or use the option.

Source facts

Netgate states that pfSense delivers DNS search domains through DHCP option 119 to clients requesting it. Client support is not universal, including older Windows DHCP clients described in the guide. For clients that cannot use the option, the source identifies Group Policy as an alternative configuration path rather than changing the DHCP server brand.

Source: Netgate — Using DHCP Search Domains on Windows DHCP Clients.

Applicability

This concerns DHCP-delivered DNS search-domain lists.

DSE recommendation

DSE recommends recording the client operating system and its supported configuration method before editing the firewall. Check whether local settings, domain policy, or endpoint management overrides the received list. Keep the intended suffix order documented because short-name lookups can resolve differently when that order changes. Prefer fully qualified names for critical service checks so a search-list fault is not confused with a missing authoritative record. Group the pilot by actual client capability and management method. Preserve the effective suffix list and the option request evidence together for each group. Where policy supplies the setting, name that owner explicitly so a DHCP change is not credited for a result produced elsewhere.

Verification

On an approved representative client, inspect the DHCP request and effective DNS search list after renewal. Compare a fully qualified lookup with a short-name lookup. If option 119 is absent or ignored, use the supported client-management method and verify the resulting configuration without repeatedly changing unrelated DHCP settings.

Official reference

Netgate — Using DHCP Search Domains on Windows DHCP Clients. Reviewed October 20, 2026.