# Event subdomain DNS delegation: operator handoff sheet

Use this worksheet before allowing a vendor or separate team to operate `tickets.example.org` or another child zone. Replace example names. Store account IDs, never passwords or API keys, in the shared sheet.

**Parent domain:** ______  **Child zone to delegate:** ______  **Event / edition:** ______

**Parent DNS operator and account:** ______  **Child DNS operator and account:** ______

**Change approver:** ______  **Change window:** ______  **Rollback owner:** ______

## 1. Decide whether a child zone is necessary

**Names the other operator must manage:** ______

**Why a record in the existing zone is insufficient:** ______

**Which names remain with the parent operator:** ______

Delegation at `tickets.example.org` transfers DNS authority for that name and names below it. A CNAME to one event platform does not transfer DNS-zone control.

## 2. Prepare and compare records

| FQDN | Type | Current answer / owner | Required child-zone answer | Dependency (web, email, verification, callback) | Verified by / date |
| --- | --- | --- | --- | --- | --- |
| tickets.example.org | [A/CNAME/etc.] | [current target] | [target] | [registration page] | [person/date] |
| api.tickets.example.org | [type] | [target] | [target] | [checkout callback] | [person/date] |
| [name] | [type] | [target] | [target] | [purpose] | [person/date] |

**Child zone nameservers exactly as assigned by provider:** ______

**Child zone SOA/NS confirmed by receiving operator:** ______

**DNSSEC/DS, wildcard, certificate and provider-specific setup reviewed:** ______

## 3. Publish parent-zone NS and observe

**Existing parent records at/below the cut reviewed:** ______

**NS records published for exact child name:** ______

**Parent authoritative NS response:** ______  **Child authoritative answers:** ______

**Normal resolver observed answer / time:** ______

**Attendee checks:** event page ______, registration ______, checkout return/callback ______, confirmation email ______, staff/support link ______.

Do not accept a fixed propagation estimate instead of observed answers. Retain the previous zone export and a reachable reversal owner until the flows above are checked.

## 4. Keep control and plan exit

**Who can edit parent NS:** ______  **Who can edit child records:** ______

**Child-zone billing owner:** ______  **Access handover if vendor leaves:** ______

**Next review / end of event:** ______  **Retirement or migration plan:** ______

Do not delete the child zone while the parent still delegates to its nameservers.

Sources: [Amazon Route 53 subdomain routing](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-routing-traffic-for-subdomains.html), [Cloudflare subdomain delegation](https://developers.cloudflare.com/dns/zone-setups/subdomain-setup/setup/), [Azure DNS delegation overview](https://learn.microsoft.com/en-us/azure/dns/dns-domain-delegation).