Spaceship

Configuration

To use this provider, add an entry to creds.json with TYPE set to SPACESHIP along with an API key and secret created in Spaceship API Manager.

Grant the key dnsrecords:read, dnsrecords:write, domains:read, and domains:write scopes.

Example:

creds.json

{
  "spaceship": {
    "TYPE": "SPACESHIP",
    "api_key": "your-spaceship-api-key",
    "api_secret": "your-spaceship-api-secret"
  }
}

The creds.json page in the docs explains how you can generate this dynamically so you can pull the secret token from 1Password or the vault of your choosing.

Metadata

This provider does not recognize any special metadata fields unique to Spaceship.

Usage

As DNS Provider only

dnsconfig.js

var REG_NONE = NewRegistrar("none");
var DSP_SPACESHIP = NewDnsProvider("spaceship");

D("example.com", REG_NONE, DnsProvider(DSP_SPACESHIP),
    A("test", "1.2.3.4"),
);

As both Registrar and DNS Provider

dnsconfig.js

var REG_SPACESHIP = NewRegistrar("spaceship");
var DSP_SPACESHIP = NewDnsProvider("spaceship");

D("example.com", REG_SPACESHIP, DnsProvider(DSP_SPACESHIP),
    A("test", "1.2.3.4"),
);

As Registrar only (DNS hosted elsewhere)

dnsconfig.js

var REG_SPACESHIP = NewRegistrar("spaceship");
var DSP_OTHER = NewDnsProvider("cloudflare");

D("example.com", REG_SPACESHIP, DnsProvider(DSP_OTHER),
    A("test", "1.2.3.4"),
);

When used as a registrar, Spaceship updates nameserver delegation. If the desired nameservers are Spaceship's hosted set (launch1.spaceship.net and launch2.spaceship.net), the provider sends provider: "basic". Any other list is sent as provider: "custom".

Activation

1. Log in to Spaceship

2. Open API Manager and create a key

3. Enable the DNS and domain scopes listed above

4. Put the key and secret in creds.json

The domain must already exist in the Spaceship account. This provider cannot create zones.

Rate limiting

Spaceship returns HTTP 429 with a Retry-After header when an endpoint's quota is exceeded. Some quotas are tight: domain info is 5 requests per domain per 300 seconds; DNS record reads and writes are 300 per 300 seconds. The provider waits and retries, honoring Retry-After, for up to 10 minutes per request.

A large push or an integration-test run can therefore pause for minutes. Increase the Go test timeout when running the suite:

cd integrationTest
go test -timeout 0 -v -args -verbose -profile SPACESHIP

Record types

Writable custom DNS types: A, AAAA, ALIAS, CAA, CNAME, HTTPS, MX, NS (non-apex), PTR, SRV, SVCB, TLSA, TXT.

TTL values are clamped to 60–3600 seconds (Spaceship's API range). A TTL of 0 becomes 3600.

Apex CNAME is allowed. Apex ALIAS is rejected because Spaceship stores it as a CNAME; declare an apex CNAME instead.

Null MX (RFC 7505, MX("@", 0, ".")) and SRV records whose target is . are not supported. The API requires a hostname for those fields and returns HTTP 422 otherwise.

Feature Summary

• Provider Type

  • Official Support: ❌

  • DNS Provider: ✅

  • Registrar: ✅

• Provider API

  • Concurrency Verified: ✅

  • dual host: ❌

  • create-domains: ❌

  • get-zones: ✅

• DNS extensions

  • ALIAS: ✅

  • CSYNC: ❌

  • DNAME: ❌

  • LOC: ❌

  • PTR: ✅

  • RP: ❌

  • SOA: ❌

• Service discovery

  • DHCID: ❌

  • NAPTR: ❌

  • SRV: ✅

  • SVCB: ✅

• Security

  • CAA: ✅

  • HTTPS: ✅

  • OPENPGPKEY: ❌

  • SMIMEA: ❌

  • SSHFP: ❌

  • TLSA: ✅

• DNSSEC

  • AUTODNSSEC: ❌

  • DNSKEY: ❌

  • DS: ❌