check per-apex slots

This block is part of the dns group and was last modified in core v15.0.0.

check per-apex slots condition v15.0.0

Report which per-apex slots a group member has filled, which it will never need, and which nobody has answered for.

In pins 5 + flow

flow
flow
Base records required
array
The group's record set, as the store holds it.
Member zone
value
The apex being checked, for example deverence.nl.
Rules
array
The group's policy. Only the per-apex entries matter here.
Own records
array
This member's own records, each carrying the slot it fills.
Slots not applicable
object
Slot name to the reason this domain will never fill it.

Out pins 7 + flow

flow
flow
Success
condition
True when the slots could be evaluated.
Member zone
value
The apex that was checked.
Slots
array
Each slot with its state, why it exists, and either what filled it or why it never will be.
Unfilled slots
array
Slots nobody has answered for.
Count
number
How many slots this group has.
Complete
condition
True when every slot is filled or explained.
Error
value
Why the slots could not be evaluated.

Reports the per-apex slot state for ONE group member without rendering anything, for a zone overview that has to show gaps before anyone renders. A slot is a record bound to one domain by something outside DNS : an ACM validation CNAME, a DKIM key, a verification token : which each apex must supply from its own records. Every slot comes back in one of exactly three states: 'filled' (an override carries it), 'not-applicable' (slots_na records the reason this domain will never have one, for example it sends no mail) or 'empty' (nobody has looked). Empty and not-applicable are deliberately NOT the same state: a zone with an empty slot is unfinished and must not be pushed, which is what complete=false and the unfilled list are for. Reads the same base_records, rules and overrides as dnszone_render_member and agrees with it by construction.

slot gaps

zone slots

A typical wiring for check per-apex slots: a function trigger starts the flow; with values feeds the base_records pin; the flow out pin feeds debug.

Used in these guides

These documentation pages use or explain this block:

DNS Zone Blocks

Version history

Introduced in v15.0.0.

Back to dns Return to the main group to view all sub-groups Back to DNS zones Return to the group to view all blocks within this group