Skip to content
AscendCore
Back to Runbook Library
Network Template: configurable per customer

DNS Record Change

Add or update a DNS record from chat behind an approval gate, with a clear change summary and a full audit record.

Integrates with

Cloudflare

The problem

DNS changes are routine until one is wrong, and then they are an outage. The balance between moving quickly and keeping a reviewed, auditable record is hard to strike with manual edits in a provider console.

What AscendCore does

A requester describes the record in Slack or Teams. AscendCore renders the change (type, name, value, TTL), routes it for approval, and on approval applies it. The change is recorded in the audit chain for traceability.

Status

Template. Supported DNS providers and approver routing are configurable per customer. Connect it to your DNS provider to enable.

Runbook source preview

Versioned, deterministic, auditable

Every runbook is defined as a versioned YAML manifest with explicit triggers, steps, and approval policies. The runbook itself is the audit-ready record of what AscendCore can and will do. Chat is just the interface that triggers it.

name: dns-record-change
trigger:
  channels: [slack, teams]
  intents: [dns_change]
steps:
  - parse_record              # type, name, value, ttl
  - render_change_summary
  - admin_approval
  - apply_record
approval:
  required: true
  approvers: [network-admins]
Want this runbook?

Configure dns record change for your environment

Templates are configurable per customer environment. Talk to us about the specific systems and approval flow you need.