Resolver Configuration

The Resolver Configuration page manages the DNS resolvers the server itself uses for outbound name resolution: the nameservers written to /etc/resolv.conf. The panel titles it Resolver Configuration (/etc/resolv.conf).

Overview

URL: /admin/settings/resolver-configuration

Navigate to Settings > DNS > Resolver Configuration.

This is a server-level setting, separate from the DNS records AdminBolt serves for hosted domains (see DNS Records). It controls which upstream nameservers the server queries when it needs to resolve hostnames itself, for example when fetching packages, validating licenses, sending mail, or issuing SSL certificates.

Fields

DNS Resolver

• Nameservers (required) - one IP address per entry, for example 1.1.1.1 and 8.8.8.8. Order matters: the first entry is queried first.

Search and domain

Both fields are optional and affect how unqualified hostnames are completed.

• Default Domain - used when no search list is specified. Leave it empty to skip.
• Search Domains - domains appended to unqualified hostnames during lookup. At most six entries, and under 256 characters in total.

Resolver Options

Advanced resolver behaviour. Each entry becomes one token on the options line of /etc/resolv.conf.

Save the form to write the values to /etc/resolv.conf.

When to change it

Leave the default resolvers in place unless you have a reason to change them, such as:

• Your provider requires specific resolver nameservers.
• You want to use a particular public resolver for outbound lookups.
• Name resolution on the server is failing and you need to point it at a known-good resolver.

Incorrect resolvers can break package installation, license validation, SSL issuance, and mail delivery. Change this only if you understand the impact, and verify that outbound DNS resolution still works afterward.

Who can do what

• Admin - views and edits the server resolver configuration. This is a node-level setting and is admin-only.
• Resellers and clients - do not have access to this page.