Administration

Administration groups the root workflows that keep SDM recoverable, accountable, secure, licensed, and maintainable.

Where to find it: Documentation > DNS Manager > Administration.

Available to: Mostly root; Security is self-service for non-root roles and License is also visible to admin.

What this page does

This section covers the platform around DNS data: node configuration, backups, user identities, audit evidence, service logs, security, licensing, and updates. These pages can affect every zone even when they contain no record editor.

Before you start

Use a named account, verify backups and alternate access, and distinguish cluster-wide settings from local settings. Schedule disruptive operating-system, SSH, TLS, restore, and update work.

Administration map

• Local Settings: hostname, interfaces, TLS, root password, SSH, OS updates.
• Backup and Restore: scheduled artifacts and selective/all restoration.
• Users: panel/API identities, keys, status, passwords, 2FA reset, and IP rules.
• Audit: who called what and the outcome.
• Logs: service/journal messages.
• Security: self-service identity controls and root policy.
• License and Version and Updates: entitlement and software lifecycle.
• Server Audit Settings and Server Logs Settings: retention and storage.

How to use it

1. Open the page that owns the requested administrative outcome.
2. Read current state and confirm scope—node, cluster, account, or product.
3. Create a backup and alternate access plan for disruptive work.
4. Make one bounded change.
5. Verify the owning status, Audit, Logs, and customer-facing behavior.

Result and next check

The administrative change is limited to its intended scope and leaves SDM reachable, observable, and recoverable. Unrelated DNS data and provider state remain untouched.