Publishing DNS Records in Bulk

Set up many domains in one go, through the DNS connections that hold their zones. Palisade previews every record for every domain, you untick anything you would rather do by hand, and one click publishes the rest.

note

This step appears only for domains whose zone sits in a connected account. Domains in no connected account keep their own setup pages, and Palisade says how many were left out and why.

Where to find it

• When adding domains. After a bulk add finishes processing, Palisade checks which of the new domains a connection covers and, if any are, shows this step before the usual one-at-a-time setup. If none are, the step skips itself.
• From the domain list. Select domains, then choose Publish DNS records from the bulk actions. It opens on a page of its own, so a long selection has the whole screen. This is the path for domains that were added before the provider was connected.

What the preview shows

Palisade reads each zone through its connection and compares what is published with what it wants for the domain. Each domain is one row, with a summary such as 2 records to add, 1 record already in place. Show records opens the detail, where every record carries a badge:

Badge	Meaning	Ticked by default
Will be added	Nothing of this kind is published at this name yet.	Yes
Will be replaced	A record of this kind exists with a different value. The current value is shown beneath the new one.	Yes
Will delete N records	Records already at this name cannot sit beside the one Palisade wants, so publishing deletes them first. The records that would go are spelled out.	No. A deletion is opted into.
Needs your attention	Several records of this kind are published, or one that cannot share the name. Palisade will not choose between records it did not publish. Clear the extra records at your provider, then preview again.	Cannot be ticked
Required	The DMARC record. It is what Palisade monitors through, so it goes with every domain set up here. Untick the domain itself to leave it out.	Locked on

A record with no badge is already exactly what Palisade wants, and nothing will be written for it.

Hosting choices

Above the list, For every domain sets which hosted records the batch should use:

• Hosted DMARC publishes a CNAME pointing at Palisade rather than a TXT record, so a policy change never needs your DNS again. See Hosted DMARC.
• Hosted SPF takes each domain's current SPF record from the zone as the starting point, then builds and flattens the hosted record from it. A domain with no SPF record, or with several, is not switched on: its row shows the record Palisade would publish, marked Needs your attention, and says why. A record that authorises no sender yet could disrupt legitimate mail, and Palisade will not choose between records it did not publish. Both are solved later, from the task on the domain's own page. See Hosted SPF.
• Hosted DKIM copies the selectors already published under _domainkey into a zone Palisade hosts before offering the delegation, so nothing stops resolving. A name already delegated elsewhere is left alone. See Hosted DKIM.

Each switch starts on only when every domain in the batch already has the feature. Switching one on turns the feature on for every domain that does not have it yet, reading each zone first, and refreshes the preview. Switching it off leaves those records out of this publish; domains already using the feature keep it. Nothing is ever turned off from here.

What happens when you publish

Palisade re-reads each zone as it publishes. A record that changed after the preview is left alone rather than overwritten, and the domain is reported as not set up, because it is not.

Each domain then shows an outcome:

Outcome	Meaning
Set up	Every record Palisade wanted for this domain is published. It needs no further setup and is left out of the one-at-a-time queue.
Partly set up	Some records published and some did not. Each one that did not is listed with the reason. A record you unticked counts here too: a domain is only set up when it holds everything Palisade wants.
Not set up	None of the records published. Each is listed with what stopped it.
Not in this account	The connection could no longer find a zone for the domain. It may have been moved or removed since the preview.
Not looked after by this connection	The connection was told to leave this domain alone. Switch it back on from the connection's zones page under Integrations. This is a decision, not a fault.
Provider did not answer	Nothing was attempted for this domain. Try again in a moment.

And each record that did not publish shows why:

Record result	Meaning
Left alone	The record changed after the preview. Preview again to publish it.
Could not publish	The provider refused the write. Its own message is shown.
Not published by Palisade	Not a record Palisade may publish on your behalf.

Anything short of Set up goes back to the domain's own setup page, where the same records can be published one domain at a time.

Limits worth knowing

• A batch previews and publishes in pages, so a hundred domains is several requests rather than one. Every request costs a zone listing per connected account, which counts against your provider's API quota.
• A conflict at a name counts against the domain even when every other record published. Palisade will not write into a name it cannot read cleanly.