# Event subdomain delegation handoff

Copy this record for each proposed child zone. Example names are placeholders. This is an ownership and verification card, not a provider-specific DNS command sequence.

## Decision

- Registered parent domain:
- Exact proposed child zone (for example, `tickets.example.org`):
- Why ordinary records in the parent zone are insufficient:
- Provider documentation requiring delegation (link and review date):
- Alternative considered: A/AAAA/CNAME or provider verification record:
- Parent-zone owner and approval contact:
- Child-zone operator and approval contact:
- Event owner who accepts visitor impact:
- Change window and time zone:

## Dependencies and preflight

| Name and record type | Current answer and owner | Needed child-zone answer | Attendee task affected | Checked by |
| --- | --- | --- | --- | --- |
| Child-zone apex (for example, `tickets.example.org`) | | | | |
| A nested hostname | | | | |
| Certificate-validation record, if used | | | | |
| Email or verification record, if used | | | | |

- Child zone exists at the intended provider: yes / no / not applicable
- Exact child authoritative nameserver set from provider (no guessed examples):
- Child records queried directly from those authoritative servers; evidence and timestamp:
- DNSSEC/DS treatment reviewed with both DNS operators and parent owner; provider guide:
- Existing parent-zone records beneath the delegation point inventoried; migration disposition:
- Parent-zone NS change approved by:
- Reversal owner, prerequisite records and decision point:

## Change and observed result

| Check | Expected evidence | Observed evidence and UTC time | Reviewer |
| --- | --- | --- | --- |
| Parent authoritative answer for child NS | Exact intended nameserver set | | |
| Child authoritative answer for each needed service | Intended records present | | |
| Independent resolver checks | Answers converge to intended child data | | |
| Event page, ticket/registration link and email tasks | Tasks work for real users | | |
| Certificate and verification checks | Provider shows valid state | | |

- Unexpected answer, owner and attendee-facing impact:
- Decision: continue / pause / reverse / escalate
- Old records or zone retained until (measurable condition):
- Final parent and child operator contacts:
- Next review date and event-season handback owner:

Do not put registrar credentials, API tokens, transfer codes or private keys in this card. Keep the DNS record values and evidence in an access-controlled project location.