# Event-domain DNS change request and approval card

One card per reviewed change or coordinated batch. Link to a ticket or infrastructure commit. Do not put passwords, API keys, attendee data or private payment details in this shared card.

**Request ID:** ______  **Event / edition:** ______  **Requester:** ______  **Requested date/time and time zone:** ______

**Authoritative DNS provider / account and zone:** ______  **Business/service owner:** ______  **DNS implementer:** ______

## Purpose and affected journey

**Why this is needed now:** ______

**Affected public names and paths:** ______

**Dependencies checked:** website ______, registration ______, checkout/callback ______, mail ______, certificate ______, redirects ______, other ______.

## Exact before-and-after record request

| FQDN | Type and provider-specific selector/routing policy | Current value(s) | Proposed value(s) | Current → proposed TTL | Source / service ID | Reviewer note |
| --- | --- | --- | --- | --- | --- | --- |
| tickets.example.org | CNAME | [old target] | [new target] | [old → new] | [ticket provider instruction] | [note] |
| [name] | [type] | [value] | [value] | [old → new] | [source] | [note] |

**Dated zone export or current-state evidence:** ______

**Technical reviewer approval / time:** ______  **Business owner approval / time:** ______

## Execution, verification and reversal

**Planned window and affected audience:** ______

**Baseline DNS query and expected response:** ______

**Expected authoritative response after change:** ______

**Real attendee/staff path to test and tester:** ______

**Conditions that trigger reversal:** ______  **Exact old values retained at:** ______  **Reversal owner:** ______

**Actual change ID or commit / execution time:** ______

**Provider status:** ______  **Authoritative answer:** ______  **Independent resolver answer:** ______

**Event path result:** ______  **Verifier / time:** ______  **Request accepted or follow-up ID:** ______

For Route 53, an `INSYNC` change status means the change reached its authoritative DNS servers; it does not prove that every resolver or attendee journey has updated. Other providers have their own status semantics. Close the card only after the planned observations are recorded.

Sources: [Amazon Route 53 record-change API](https://docs.aws.amazon.com/Route53/latest/APIReference/API_ChangeResourceRecordSets.html) and [GetChange status](https://docs.aws.amazon.com/Route53/latest/APIReference/API_GetChange.html).