Apply approved DNSSEC changes from compliance tasks
Keep a defined DNSSEC compliance task moving by checking for it on schedule and applying only an explicit, approved status change.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Update DNSSEC Status
Tool to update DNSSEC configuration for a zone. Use when you need to enable or disable DNSSEC or adjust DNSSEC options after confirming the zone ID.
Why this helps
DNSSEC actions can be easy to overlook, and making a status change without confirming the zone and intended direction creates avoidable risk.
- Check a specified DNSSEC task on a recurring schedule.
- Require an explicit enable or disable instruction and a confirmed Cloudflare zone.
- Report the outcome so the compliance task can be followed up.
Setup
Build it in a few focused steps.
- 1Connect 21risk and Cloudflare api key once in the Notis portal.
- 2Create an automation in the portal, or tell Notis to create one, and give it a clear name.
- 3Describe the outcome in one instruction: update DNSSEC only for an approved request that names the zone and explicitly states whether to enable or disable it.
- 4Pick a recurring Notis schedule and choose where run reports should go.
- 5Test with one real approved DNSSEC request and verify the status in Cloudflare.
Questions about this workflow
Does the workflow handle registrar changes too?
No. The Cloudflare action updates DNSSEC configuration for the zone. If disabling DNSSEC requires a registrar change, that step is outside this Cloudflare action.
Can the automation decide whether DNSSEC should be enabled?
No. The compliance request needs to state the approved direction explicitly. The automation should not infer it.
What if the schedule finds no matching request?
It should make no Cloudflare change and report that no qualifying request was found.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 21risk to Cloudflare api key. A trigger fires from one place; an action lands in another.
21risk triggers
Cloudflare api key actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create DNS Record
Tool to create a new DNS record in a Cloudflare zone. Use when you need to add a record (A, CNAME, TXT, MX, etc.) to a specified zone.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Zone Lockdown Rule
Tool to create a Zone Lockdown rule. Use when you need to restrict access to specific URL patterns to defined IPs/CIDR ranges. Use after confirming zone_id.
Create Rule in Ruleset
Tool to add a rule to an existing ruleset. Use when you need to append or insert a new rule in a Cloudflare ruleset.
Create Ruleset
Tool to create an account- or zone-scoped ruleset. Use after defining your ruleset details and selecting the correct scope.
Delete DNS Record
Tool to delete a DNS record. Use when you need to remove a specific DNS record from a zone after confirming both zone and record IDs.
Delete DNSSEC
Tool to delete DNSSEC records for a zone. Use after disabling DNSSEC at the registrar to remove DNSSEC configuration.
Delete Rule from Ruleset
Tool to delete a specific rule from a ruleset. Use when you need to remove an outdated or incorrect rule from an account or zone ruleset after confirming IDs.
Delete Ruleset
Tool to delete all versions of a ruleset. Use when you need to remove a ruleset from an account or zone after confirming no references exist.
Connect any two apps with Notis in the middle.
21risk and Cloudflare api key, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Cloudflare api key.