Lexicon Garden

space.highport.manage.enableDelegation

Declare a registered domain a delegation base, so its owner can reserve names directly under it for other identities, and obtain the wildcard traffic record that routes those names. The caller must be the base's registered identity, and the base must be verified or active.

Repository @lexicons.highport.space did:plc:ciygg5hma4q7ah2kxaszkyob namespace authority
Details · procedure
Kindprocedure
Authoritymanage.highport.space
Indexed

Showing version bafyreia3e2fp7defkbwzm67biroli7mrv773t2ryc6dqvmunhpkg2qmdwm. Show the latest

Compare Edit in builder → Fork →

Procedure

procedure · POST

Input

application/json

domain

requiredstring

The base: a domain registered to the caller.

  • maxLength: 253

maxNames

integer

The most names the base may hold in reservation. Omitted, the deployment's default applies; a value above the deployment's ceiling is refused.

  • minimum: 1

Output

application/json

domain

requiredstring

probeHostname

string

The random name under the base through which the wildcard is proven to route. Absent while the base has no probe.

  • maxLength: 253

records

requiredarray

The DNS records delegation asks for: the wildcard traffic record.

Errors

InvalidDomain

Not a syntactically valid domain.

NotBaseOwner

No verified or active registration of that domain belongs to the caller.

DelegationUnsupported

The domain cannot delegate names: it is registered to a space, it is a domain this deployment provides or a name under one, it was itself handed out under a base, or it sits above or beneath a domain whose delegation is not off. Delegation bases do not nest.

MaxNamesAboveLimit

maxNames is above the most names this deployment lets one base hold.

CaaForbidsIssuance

The base's CAA records do not permit this deployment's certificate issuer, account, or challenge method. The message names the record in the way.

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • space.highport.manage.setCertificateMode

    procedure

    Choose how names under a proven base get certificates. wildcard lets this service get one wildcard certificate for the base over DNS-01, through the base's own challenge target, and returns the record that delegates it. per-name ends that grant. The caller must own the base, which must be verified or active. Delegation does not need to be enabled.

  • space.highport.manage.reserveDomain

    procedure

    Reserve a name directly under a delegation base for another identity. The name answers /.well-known/atproto-did with the subject right away, and the subject can then publish a site there. The caller must own the base. Any unproven claim on the name is replaced. Repeating the call for the same subject returns the existing reservation and does not count against maxNames. Reservations last as long as the base.

  • space.highport.manage.register

    procedure

    Register a domain to the caller, or to a space the caller is the authority of, and get the DNS records needed to prove ownership and route traffic.

  • space.highport.manage.disableDelegation

    procedure

    Stop a base handing out names: remove its probe and clear its delegation state. Refused while any reservation remains; release each one with releaseReservation. A certificate grant on the base is left in place.

  • space.highport.manage.releaseDomain

    procedure

    Release a domain: deactivate its site and stop authorizing it for TLS. Certificates already issued for it stay valid until they expire. If the domain is a base with a wildcard grant, the grant ends and the wildcard is revoked and deleted; no account can take the domain until that finishes. Stored blobs are left for garbage collection.