Skip to main content

​
Overview

DNS pools group nameserver backends that process zone data. Multiple pools support geographic distribution or tiered service levels. Pool attributes control automatic zone scheduling — when a zone is created, the DNS service selects a pool based on attribute matching policies.
Administrator Access Required — This operation requires the admin role. Contact your Polystack administrator if you do not have sufficient permissions.

​
Pool Attributes and Zone Scheduling

Pools use key-value attributes to match zones during scheduling. When a zone is created without an explicit pool assignment, the DNS service selects a pool based on these attributes. Configure pool attributes through the deployment console service configuration files.

​
View Pool Information

​
Nameserver Health Monitoring

Monitor the health of pool nameservers by verifying they are authoritatively answering queries for managed zones:
Verify nameserver is authoritative
A healthy nameserver returns the SOA record with AUTHORITY: 1. If the nameserver returns SERVFAIL or does not respond, check the DNS service worker logs for synchronization errors.

​
Adding Nameservers to a Pool

Adding nameservers requires updating the pool configuration through the deployment console. After adding a nameserver:
1

Update pool configuration in the deployment console

Add the new nameserver to the pool’s nameservers and targets lists in the the deployment console DNS service configuration.
2

Deploy the configuration

Apply the updated configuration:
Deploy DNS service configuration
3

Verify the new nameserver receives zone data

Verify zone synchronization on new nameserver
Wait for the zone data to synchronize before proceeding.
4

Update external NS delegation records

Update the NS delegation records at the domain registrar to include the new nameserver. Allow 48 hours for resolver caches to propagate the new NS records globally.
Do not remove an existing nameserver from a pool until the new nameserver is fully synchronized and the old NS records have expired from resolver caches (typically 48 hours).

​
Next Steps

Backend Configuration

Configure backend driver targets for each pool

Zone Transfers

Manage zone transfer requests to secondary nameservers

Quotas

Set per-project DNS resource limits

Admin Troubleshooting

Diagnose nameserver synchronization failures