Poweradmin\Domain\Port

Who is acting in the current request: the session user on the web, the key owner on the API. Domain rules ask this instead of reading the session.

Exposes the most recent PowerDNS API error so domain checks can tell an outage from an empty backend.

Records or clears the most recent PowerDNS API error; the API client and backend provider write through this.

The audit events domain services record; the Application layer owns the line format and the actor context.

Capability probe telling callers which kind of DNS backend they hold.

Catalog zone membership reads and writes against the DNS backend.

Told about change request events so people can be notified. Implementations must not throw; a failed notification never undoes the event.

PowerDNS data access (domains, records, supermasters) over direct SQL or the PowerDNS API; Poweradmin-native tables stay on SQL.

DNSSEC operations for one zone.

Renders the account emails a preview tool can show; the Application layer owns the templates and their custom overrides.

Records login attempts and reports lockouts; the Application layer owns the storage and thresholds.

Delivers MFA email verification codes; the Application layer owns the template and transport.

Hashes and verifies user passwords; the Application layer owns the algorithm and cost settings.

Checks a password against the configured policy rules; the Application layer owns the configuration.

Merges the outbound HTTP proxy, when one applies to the URL, into a set of PHP stream context options.

Splits a hostname on the public suffix boundary, so that names under a multi-label suffix such as co.uk or com.pl are divided where registration actually happens rather than on the last dot.

Renders a string as a QR code for display in a page.

Records before/after snapshots of record and zone changes for the change log.

The per-record comment reads and writes the zone editor needs; the Application layer owns the storage.

Carries an edited record's comment over to its A/AAAA or PTR counterpart.

Record lookups by id, name or zone read from the DNS backend.

The search page's record half: matching records with their zone owner, paged and sorted, and the unpaged match count. Rows carry disabled as a bool.

Record add, edit and delete writes against the DNS backend.

A record write backend that sits behind a separate service which can refuse a write and say why (the PowerDNS API). Backends without one do not implement it.

Orders reverse zone names in PHP by the configured sort type.

Wildcard search over zones and records in the DNS backend.

SOA serial handling: whether PowerDNS bumps the serial itself and the zone serial policy metadata.

The request's session store. One implementation wraps PHP's own session, the other keeps the values in memory for tests and for request-scoped caches.

Supermaster (autoprimary) reads and writes against the DNS backend.

Time-based one-time passwords, as used by authenticator apps.

The request's unit of work: one transaction shared with every repository that writes through the same connection.

Tells PowerDNS that a zone written straight to its database changed, so a new zone is served at once and cached answers for the zone are dropped.

DNSSEC key lifecycle for a zone, plus the DS and DNSKEY records derived from its keys.

Zone lookups, listings, record counts and SOA health read from the DNS backend.

Rectifies a zone after its records change so the DNSSEC ordering data stays valid.

The search page's zone half: matching zones with their owners, paged and sorted, and the unpaged match count. Each backend keeps its own row shape.

Signing state of a zone: securing, unsecuring and reading whether it is signed.

Zone create, delete, kind, primary, account and AXFR-retrieve writes against the DNS backend.