Configure WHM Recursive Resolvers with Recovery in Mind

WHM Resolver Configuration sets the recursive DNS servers this machine uses for its own lookups. These are not necessarily the authoritative nameservers you publish for hosted domains. Choosing a resolver does not alter registrar delegation or move a zone.

Choose approved reachable resolvers

Obtain resolver addresses appropriate to this server’s network and policy. Consider private/split DNS, access controls, privacy and the applications using resolution. Do not point the server at an authoritative-only service and expect it to resolve arbitrary internet names. PowerDNS Authoritative is not PowerDNS Recursor.

Preserve the current resolver configuration and keep administrative recovery access. Wrong resolver settings can interrupt package access, outbound mail and other services even while an already-open SSH connection remains usable.

Apply through the supported interface

1. Open verified HTTPS WHM, then Networking Setup > Resolver Configuration.
2. Review the warning and proceed only with approved values.
3. Enter the primary and secondary IPv4 or IPv6 resolver addresses required by the wizard; add an optional third if it fits the design.
4. Continue and review confirmation. Preserve any network-management integration that governs these settings on the installed system.

The wizard edits /etc/resolv.conf. On other Linux setups that file can be generated or point to a local stub; do not overwrite it outside the supported management process simply because a generic tutorial does so.

Verify from this server

Check that required public and private names resolve through the configured path and that dependent applications still work. Compare a query to an explicitly chosen resolver only to isolate behavior; bypassing the normal path is not proof the application’s configured path is healthy. A primary/secondary list is not a guarantee that every resolver implementation will fail over in a particular sequence.

If a change fails, restore the verified prior configuration using the authorized recovery path. Do not disable DNSSEC validation, remove network restrictions globally or substitute random public resolvers to hide an unresolved network or private-zone problem.

Reference: WHM resolver wizard and requirements.

Reviewed October 16, 2026. No resolver file, network setting or customer lookup path was changed or tested.