ワンクリックで
sapcc-dns
// DNS zone and recordset operations via Designate. Triggers: dns, zone, recordset, domain, designate. NOT for: network ports, floating IPs (use sapcc-networking).
// DNS zone and recordset operations via Designate. Triggers: dns, zone, recordset, domain, designate. NOT for: network ports, floating IPs (use sapcc-networking).
Audit trail investigation on SAP Converged Cloud using Hermes. Triggers: audit, who changed, what happened, hermes, events, compliance, CADF, activity log, trace action, who did, what was done, event history
Autoscaling operations via Castellum. Triggers: autoscaling, castellum, resize, scaling, threshold, auto-resize, capacity management. NOT for: manual quota changes (use sapcc-quota/Limes).
Bare metal node operations via Ironic. Triggers: baremetal, bare metal, ironic, node, provision state, hardware, physical server. NOT for: virtual servers (use sapcc-compute/Nova).
Manage compute instances on SAP Converged Cloud. Covers server lifecycle, flavor selection, status transitions, and cross-service correlation with networking and storage. Use when: listing VMs, checking server status, debugging instance issues, performing server actions (start/stop/reboot), selecting flavors, or investigating why a server won't start. NOT for container workloads (use sapcc-registry) or bare metal.
Archer endpoint service management for private network connectivity in SAP Converged Cloud. Triggers: endpoint service, private link, archer, private connectivity, service endpoint, internal access, cross-project access
Email service operations via Cronus. Triggers: email, cronus, smtp, template, email usage, sending. NOT for: monitoring alerts (use sapcc-metrics/Maia).
| name | sapcc-dns |
| description | DNS zone and recordset operations via Designate. Triggers: dns, zone, recordset, domain, designate. NOT for: network ports, floating IPs (use sapcc-networking). |
| version | 1.0.0 |
| metadata | {"service":["designate"],"task":["manage","inspect","debug"],"persona":["developer","platform-engineer"]} |
Manage DNS zones and recordsets: list zones, inspect zone details, query recordsets by type.
| Tool | Purpose | Key Parameters |
|---|---|---|
designate_list_zones | List DNS zones with optional filters | name, status (ACTIVE/PENDING/ERROR), type (PRIMARY/SECONDARY) |
designate_get_zone | Full zone detail by UUID | zone_id (required) |
designate_list_recordsets | List recordsets within a zone | zone_id (required), name, type (A/AAAA/CNAME/MX/TXT/SRV/NS), status, data |
designate_list_zone_transfer_requests | List outgoing zone transfer requests | zone_id, status |
designate_list_zone_transfer_accepts | List accepted zone transfers | (none) |
| Tool | Purpose | Key Parameters |
|---|---|---|
designate_create_recordset* | Create a DNS recordset in a zone | zone_id (required), name (required, FQDN with trailing dot), type (required), records (required, comma-separated), ttl, description, confirmed |
designate_delete_recordset* | Delete a DNS recordset | zone_id (required), recordset_id (required), confirmed |
name must end with . (e.g., app.example.com.)records*_id parameters validated before API callconfirmed=trueZone names are FQDN with trailing dot. Designate stores zone names like example.com. (note the trailing dot). When filtering by name, include the trailing dot or you will get zero results.
zone_id is required for recordsets. You cannot list recordsets globally — you must first identify the zone UUID, then query recordsets within it. Always call designate_list_zones first if you only know the domain name.
Status PENDING means propagation in progress. A zone or recordset in PENDING status has been accepted but is not yet live on nameservers. Do not treat PENDING as an error — wait and re-check.
Recordset type must be uppercase. The type filter expects uppercase values like A, CNAME, MX. Lowercase values will return no results without an error.
Multiple records per recordset. A single recordset (e.g., type A) can contain multiple IP addresses in the records array. This is normal for round-robin DNS.
SOA and NS recordsets are auto-managed. Every zone has system-created SOA and NS recordsets. These cannot be modified and should be ignored when auditing user-created records.
Serial number increments on every change. The zone serial field is useful for verifying whether a recent change has been applied — compare before and after values.
designate_list_zones with name=example.com. — get the zone UUID.designate_list_recordsets with zone_id=<uuid> — retrieve all recordsets.type if you only need specific record types (A, CNAME, etc.).designate_list_zones with name=<domain.> — confirm the zone exists and status is ACTIVE.designate_list_recordsets with zone_id=<uuid> and name=<fqdn.> — check if the expected recordset exists.designate_list_zones with status=ERROR — find zones in error state.designate_get_zone to inspect details and timestamps.hermes_list_events for the triggering action.| Need | Service | Tool |
|---|---|---|
| Who modified a zone/recordset | Hermes | hermes_list_events(target_type=zone) |
| DNS quota for the project | Limes | limes_get_project_quota(service=dns) |
| Floating IP that should have a DNS record | Neutron | neutron_list_floating_ips |
| Server associated with an A record IP | Nova | nova_list_servers + filter by IP |