Resolver Configuration in WAP
Configure public or custom DNS resolvers for the Eenos server, understand required IPv4 and optional IPv6 fields and verify changes.
Open Eenos → Preferences → Resolver Configuration to choose the DNS resolvers used by this server for domain and network lookups. This is separate from the authoritative nameserver defaults in Basic Setup.
Before you begin
Sign in to WAP as an administrator over HTTPS. Obtain reachable recursive resolver addresses from your network provider or choose one of the supplied public presets. Check that network routing and firewall policy permit the intended DNS traffic. Keep the previous resolver settings and an independent server-access method available. Demo sessions cannot apply changes.
This replaces the system resolver configuration
The handler replaces /etc/resolv.conf and removes an existing symlink at that path before writing. Existing search domains, options and nameserver entries are not preserved by this operation. Coordinate with any operating-system or network tool that manages that file before applying a change.
Public DNS Resolvers
| Button | Addresses applied by the current preset |
|---|---|
| Deploy Cloudflare Resolver | 1.1.1.1, 1.0.0.1, 2606:4700:4700::1111, 2606:4700:4700::1001 |
| Deploy Google Resolver | 8.8.8.8, 8.8.4.4, 2001:4860:4860::8888, 2001:4860:4860::8844 |
Select one deployment button to apply its preset. It does not append the preset to your custom entries. Both presets include IPv6 addresses; verify the chosen configuration is appropriate for this server's connectivity. These are the values built into Eenos, not a recommendation that one provider suits every network.
My Own Private Resolvers
The custom fields display addresses from the panel's saved resolver settings, grouped into IPv4 and IPv6. They are not a fresh inspection of every resolver setting managed by the operating system.
| Field | Required | Accepted value |
|---|---|---|
| Primary Resolver IPv4 | Yes for custom setup | One valid IPv4 resolver address. |
| Secondary Resolver IPv4 | No | One additional valid IPv4 address. |
| Tertiary Resolver IPv4 | No | One additional valid IPv4 address. |
| Primary Resolver IPv6 | No | One valid IPv6 resolver address. |
| Secondary Resolver IPv6 | No | One additional valid IPv6 address. |
| Tertiary Resolver IPv6 | No | One additional valid IPv6 address. |
Enter addresses alone, without ports, subnet suffixes or URLs. The form recommends at least two resolvers for reliability, but the actual server validation requires the first IPv4 field and validates each other populated field. An IPv6-only custom submission does not pass this form.
Apply and verify
- Record the existing settings and check how the operating system manages DNS resolution.
- For custom setup, fill Primary Resolver IPv4 and the additional addresses you intend to use.
- Select Setup Resolver, or select a public preset's deployment button instead.
- Review the result message. Success is reported as DNS resolver configured successfully, Cloudflare DNS resolver configured successfully or Google Public DNS resolver configured successfully.
- Reload and inspect the saved address fields. Independently verify that the server can resolve the names it needs, including internal names when applicable.
Custom addresses are written in field order, with empty fields omitted. The handler writes the system resolver file and saves the address list for the panel. Attempted updates are recorded in configuration audit events. The handler does not perform a DNS query or prove resolver reachability before reporting success.
Errors and recovery
| Message or situation | Action |
|---|---|
| Please enter at least one resolver IP address | Populate Primary Resolver IPv4 for custom setup. Other fields alone do not satisfy this check. |
| Invalid IPv4/IPv6 or form-validation error | Put each address in a field of its matching address family and remove ports or subnet suffixes. |
| Demo server: this operation is unavailable | Changes cannot be applied in this session. |
| Unable to configure DNS resolvers | Inspect the actual system resolver state and server-side write error before retrying. Failure may occur after part of the operation. |
| Saved fields look correct but resolution fails | Verify routing, firewall policy, the resolver's permissions and any other tool rewriting system DNS configuration. |
Restore the previous address list through custom setup if that is sufficient. If the original configuration relied on a symlink, search options or an operating-system service, recovery may require restoring that arrangement outside this page.
Do’s and don’ts
- Do use recursive resolvers reachable and permitted from this server.
- Do account for internal domains before replacing provider/private resolvers with public ones.
- Do verify name resolution after applying the change.
- Do not use authoritative nameservers simply because they host your domains; they may not permit recursive queries.
- Do not assume listing six addresses means the operating system will use every address equally.
- Do not assume a success message guarantees network reachability or preserves previous resolver options.
Previous: Change Hostname. Next: API Manager.