Domains and DNS

The Domains screen lists every domain the Manager knows about. Opening one gives you four tabs: DNS, Registrar, Email forwarding and Sending.

The Domains list

The search box is labelled Filter domains… and matches the domain name. Every column header sorts, gaining a ↑ or ↓ when active. The columns are:

Paging matches the rest of the dashboard: 24, 48, 96 or 240 per page with Per page, «, ← Prev, Next → and ». The count pill beside the title reads 94 domains.

Right-click a row for Open domain, Visit site ↗, Copy domain and, for operators, Delete domain….

There are no filter chips and no bulk actions on this screen.

Adding a domain

+ New domain in the top bar opens the New domain dialog. Fill in Domain, then pick an Account (operators) or a Website (customers, and it is required). The DNS zone toggle decides whether a zone is created here; its label reads “On — records editable here” or “Off — DNS stays external”.

Domain detail

The header shows the domain name, then a status line reading whether DNS is active and where the domain is registered, then the accounts it belongs to. Operators get Delete domain… at the top right.

Account assignment

Under the status line, the word Account is followed by a chip per assigned account. Operators get an ✕ on each chip (title="Unassign account") and a + Assign… pill that opens the Assign an account dialog. Search accounts, and each row shows its site count and plan with an Assign action. A domain can belong to more than one account.

DNS zone editor

The DNS tab edits the domain’s zone. Its explainer reads: “Click a record to edit. Changes are staged locally, then saved to the zone as one bulk update.”

Supported record types are A, AAAA, ANAME, CNAME, MX, TXT, SPF, SRV and HTTP.

Adding and editing

To add a record, use the bar at the bottom of the records card: pick a type, enter a name (@ for the root), enter a value, then click Add record. New records default to a TTL of 3600.

To edit a record, click its row. It expands in place with a name field, a value field, a TTL field, and Done and Cancel. Multi-value types get sub-rows instead of a single value field: MX takes a priority and a server, SRV takes priority, weight, port and host, and everything else takes repeated value fields. Each value has an ✕ (title="Remove value") and there is an + Add value link.

Records are stored one per name and type, with values stacked inside. Adding a value for a name and type that already has a record folds into that record rather than creating a duplicate. CNAME and HTTP stay single-value.

To delete a record, click Delete on its row.

Saving

None of the above touches the zone until you save. Once anything is staged, a banner appears reading Unsaved zone changes with Discard and Save zone. Discard re-fetches the zone. Save zone is the bulk save: it commits each added, edited and deleted record and then reloads the zone. If some changes fail, the banner reports how many.

Before saving, values are autocorrected the way the legacy editor did: a CNAME or ANAME value, an MX server or an SRV host missing its trailing dot gets one, and a TXT value typed without quotes is wrapped in them.

Import and export

Import zone… opens a dialog subtitled “paste a BIND zone file — records are staged, nothing saves until you Save zone”. Paste a zone file and the parsed records preview live, counted as 14 records parsed. Then choose Append to editor to add them to what is there, or Replace zone, which stages the removal of every existing record first. Either way you still have to press Save zone.

Export BIND downloads the zone as a BIND zone file, built from the live SOA and NS records plus every A, AAAA, CNAME, MX, SRV and TXT record, with long TXT values split into chunks.

When there is no zone

If the domain has no zone here, the tab reads “No DNS zone is active for this domain.” with an Activate DNS zone button.

At the bottom of the tab, operators get a teardown control: “Removes every record and the zone itself at Constellix.” with a Delete DNS zone button. Its confirm warns that the domain stops resolving through your nameservers.

Registrar

The Registrar tab has a Registration card on the left and Nameservers and Contacts on the right.

Registration

The Registrar row names the connection and its remote status, or reads External. Operators get an Edit pill that opens Where is this domain registered?. That dialog lists each registrar connection you have configured, labelled as a Hover.com connection or a Spaceship connection, plus a final Registered externally row for domains managed elsewhere. Each row’s action reads Current or Select. Choosing one updates the Domains list column and the domain header immediately.

An external domain shows: “This domain is registered externally. Renewal, transfer locks and contacts are managed at its current registrar.” and the rest of the card collapses.

A connected domain gets two toggles:

• Transfer lock reading On or Off
• WHOIS privacy reading On or Off

Below them is Auth code, masked until you click Copy. That fetches the transfer authorization code from the registrar and puts it straight on your clipboard, which is how you hand a domain to another registrar.

Hover.com and Spaceship are the two registrar integrations. Everything else is external.

Nameservers

The Nameservers card lists the current nameservers, sourced from the registrar when one is connected and from the zone otherwise. With a registrar connected you get an Edit link, opening Edit nameservers: one nameserver per line, with the note that changing away from the hosted DNS disables the zone editor here. Save with Save nameservers.

Contacts

With a registrar connected, the Contacts card summarises the registrant and offers Edit contacts. The dialog covers Name, Organization, Email, Phone, Address, City / State and Country, and applies to all four roles: registrant, admin, tech and billing.

Email forwarding

Forwards route through Mailgun on the root domain, and new addresses verify automatically.

If forwarding is not set up, the tab offers Activate forwarding. Activation creates the Mailgun domain, writes the MX, TXT and CNAME records it needs into the hosted DNS zone, and asks Mailgun to verify. If the domain already has MX records, you are asked to confirm overwriting them with Overwrite MX records.

While the domain is unverified you get a card headed Domain not yet verified with the note that DNS changes can take up to 24 hours. Two sections list what is outstanding: Sending / verification records with a name and value per record, each with a Copy link, and Receiving records (MX) with the priority prefixed into the value. Two buttons sit below: Verify DNS records, which asks Mailgun to re-check, and Add records to Anchor DNS when the zone is hosted here.

Once active, the tab lists each forward as alias@domain → destination, with a status reading Verified, Pending verification or Catch-all, and a Delete link. To add one, fill the alias field (or * for a catch-all), the destination, and click Add forward.

Operators get a teardown control at the bottom: Delete email forwarding, which removes the Mailgun forwarding zone and every alias on it.

Sending

The Sending tab manages the domain’s transactional sending zone, normally mg.<domain>. Its header reads the zone and its state, with Suppressions and Deploy to… buttons.

If sending is not set up, the tab offers Set up mg.. Setup creates the Mailgun sending domain, writes its records into the hosted zone when there is one, and asks Mailgun to verify.

DNS verification

The DNS verification card lists every record the zone needs. That is the SPF, DKIM and tracking records plus the MX records, so nothing a sending zone needs is missing from the table. MX rows carry the priority prefixed into the value, the way a zone file writes it. Each row shows its status as Verified or Pending, and pending rows get a Verify link.

Copy DNS records in the header hands you the whole set as plain text, ready to paste into a ticket or send to a customer’s DNS provider. It starts with a header line naming the domain, then Type, Name and Value lines per sending record, and Type, Name, Priority and Value per receiving record.

Usage, events and suppressions

A Usage card switches between Daily, Monthly and Yearly and shows Sent, Delivered, Failed and Delivery rate tiles over a bar chart. A Recent events card lists the latest deliveries with their event, subject and recipient.

Suppressions opens a dialog with Bounces, Unsubscribes, Complaints and Allowlist tabs, each row with a Remove action.

Deploy to… configures SMTP on a connected site with this zone’s credentials. Filter the site list, pick one, then supply a Send from name and click Deploy. The Mailgun SMTP password is never sent to the browser.

Operators get a teardown control at the bottom: Delete sending zone, which removes the Mailgun sending domain and its SMTP credentials, stopping mail from any site using them.

What is not here

There is no expiry column on the list and no expiry row on the Registrar tab, because the domain list payload carries no expiration date. There is no renew button and no auto-renew toggle. Deleting a domain does not cancel its registration at the registrar; the confirm dialog says so and enumerates what the delete does cascade to, namely the DNS zone, email forwarding and the Mailgun sending zone.

Related

• Accounts and billing
• WP-CLI commands for wp captaincore dns and wp captaincore mailgun
• Source: CaptainCore/captaincore-manager