A database-backed nameserver.
WHAT DISTINGUISHES IT
Separation of the authoritative server, the recursor and the load balancer into distinct products Backends storing zones in databases rather than files
WHAT DATABASE BACKENDS PROVIDE
Zones managed through a database or an interface Easy integration with provisioning systems Replication using database mechanisms
WHY THAT SUITS HOSTING PROVIDERS
Zones can be created and modified by the control panel directly, at scale.
WHAT THE API PROVIDES
Programmatic management of zones and records.
WHAT THAT ENABLES
Automation, and integration with billing and provisioning.
WHAT THE RECURSOR IS
A separate product for resolving on behalf of clients.
WHY SEPARATION MATTERS
Authoritative and recursive roles have different exposure and different tuning.
WHAT THE LOAD BALANCER PRODUCT PROVIDES
Filtering, rate limiting, and distribution in front of resolvers.
WHAT IT SUITS
Protecting resolvers from abuse and attack.
WHAT TO CONFIGURE
Backend credentials securely Replication between servers DNSSEC signing, where used
WHAT TO MONITOR
Database availability, since the nameserver depends on it.
WHAT TO PLAN
Behaviour when the database is unreachable.
