WAP Basic Setup
Configure shared IPv4 and IPv6, server contact emails, account home directories and default nameservers in Eenos WAP.
Use Eenos → Preferences → Basic Setup to configure shared hosting addresses, administrator contacts, account home-directory locations and default authoritative nameservers.
Before you begin
- Sign in with administrator access. See First Login.
- Confirm the intended server and record its current values before changing them.
- Have the server's assigned shared IPv4 address ready. Use IPv6 only if configured for this server.
- Prepare hosting account storage locations and working contact email addresses.
- Plan authoritative nameservers, their DNS records and any registrar glue separately.
The form can be viewed in demo mode, but saving is disabled there.
Preferences do not provision the underlying resources
Saving records panel preferences and updates shared-IP usage tracking. It does not configure network interfaces, create directories, move existing accounts, register nameservers or rebuild existing DNS zones and web configurations.
Server Information
| Field | Required | Value and validation |
|---|---|---|
| Main Shared IPv4 Address | Yes | A valid primary shared IPv4 address. Enter the address without a subnet suffix or port. |
| Main Shared IPv6 Address | No | A valid IPv6 address; leave blank if not configured. A supplied value is saved in expanded notation. |
| Server Contact Email | Yes | One or more valid email addresses separated by commas. Surrounding spaces and empty entries are removed; each remaining email is validated. |
Contact addresses are intended for server alerts and notifications. Saving does not send a test email. IP checks validate format, not ownership, interface configuration or reachability.
User Home Directories
| Field | Required | Value and validation |
|---|---|---|
| Primary Home Directory | Yes | Default parent location for account homes, such as /home when that is the server's intended location. |
| Additional Home Directories | No | Additional parent locations separated by commas, such as /home2, /home3 when those locations have been prepared. Leave blank if none are needed. |
Each nonempty additional path is trimmed and checked by the path validator. These checks do not verify existence, mounts, permissions or free space. Verify storage separately. Supply a parent hosting location, rather than an individual account's full home path.
Changing these preferences does not relocate existing account data.
Default Name Servers
These are authoritative nameserver defaults assigned during account creation. Recursive resolvers used by the server belong under Resolver Configuration, a separate menu.
| Field | Required | Value |
|---|---|---|
| First Name Server (NS1) | Yes | Valid nameserver domain name, such as ns1.example.com. |
| Second Name Server (NS2) | No | A second nameserver domain name, if used. |
| Third Name Server (NS3) | No | An optional third nameserver domain name. |
| Fourth Name Server (NS4) | No | An optional fourth nameserver domain name. |
Enter hostnames, not IP addresses, URLs or names with ports. Domain normalization removes a trailing dot and converts internationalized domain names to DNS-compatible form before validation.
Only populated entries are saved, in entered order. Leaving a gap compacts the list, so values can appear in earlier slots after reload. NS2 is optional in this form, as are NS3 and NS4.
Saving does not create A/AAAA records, registrar glue or domain delegation, and does not rewrite existing account zones. Complete those tasks in the relevant DNS and registrar tools.
Existing values and defaults
The page shows saved server settings rather than imposing universal defaults. Placeholder nameservers are examples. Saved additional home locations appear as comma-separated values.
All fields are submitted together. Clearing optional IPv6, additional locations or optional nameservers removes those values from these preferences; it does not remove interface addresses, delete directories or remove registrar records.
Save Changes
- Review Server Information, including shared addresses and each contact recipient.
- Review the primary and additional account home-directory locations.
- Enter NS1 and the additional nameservers you intend to use.
- Select Save Changes.
- Look for Basic settings saved successfully.
- Reload the page and confirm the saved values. Expanded IPv6 notation and compacted nameserver slots are expected.
The server validates the full form before writing preferences. After a successful preference write, it updates main shared-IP usage tracking and records a configuration audit event.
Verify the operational result separately
The success message confirms the preference file was written. It does not verify DNS, email delivery, network connectivity or storage readiness. Review any dependent configuration separately.
Errors and recovery
| Message or situation | What to do |
|---|---|
| Please correct the validation errors and try again | Check required fields, address formats, each contact email, home paths and nameserver hostnames. Review all fields before submitting again. |
| Demo server: this operation is unavailable | The session cannot save these settings. |
| Unable to save the basic settings due to an I/O error | Reload to inspect the saved state, then investigate the server-side storage or permission error before retrying. |
| Values appear unchanged after a failed submission | Several fields display saved values again. Do not assume every unsaved edit is retained. |
| Save succeeded but an existing website is unchanged | Basic Setup does not migrate existing accounts or regenerate their configuration. Use the relevant account, DNS or IP-management tool. |
To correct an unintended preference, reopen the page, restore your recorded previous values, save and verify them. This restores preferences only; separate changes made in other tools need their own review.
Do’s and don’ts
- Do use assigned server addresses and prepared account storage paths.
- Do choose monitored contact addresses and verify notification delivery separately.
- Do check DNS and registrar requirements before using new nameserver defaults.
- Do retain previous values when planning a change.
- Do not treat successful format validation as proof that a resource is operational.
- Do not use these settings as a shortcut for migrating existing hosting accounts.
- Do not confuse authoritative nameservers with recursive DNS resolvers.
Next: Server Time. See the Dashboard guide for the server overview.