Expand description
Zone data types — the pure request/response and configuration structs.
These are the types a library consumer needs in order to talk to bindcar’s
zone API, with no HTTP machinery attached. They are deliberately free of
axum, ApiError and AppState so that a consumer importing only
bindcar::ZoneConfig does not inherit the server stack.
The HTTP handlers that consume these live in crate::zones, which
re-exports everything here so existing bindcar::zones::ZoneConfig paths
keep working.
See .github/community/02-feature-gate-http-server.md — this split is
phase 1 of putting the server behind a cargo feature.
Structs§
- Checkds
Request - Request body of
POST /api/v1/zones/{name}/dnssec/checkds(ADR-0001): tells named that the DS for a key was published at, or withdrawn from, the parent zone — required to complete rollovers and the gracefulinsecuretransition when no parental agents are configured. - Create
Zone Request - Request to create a new zone
- DnsRecord
- DNS record entry
- DsRecord
View - One DS record of a zone, ready to publish at the parent (ADR-0001).
- DsSet
Response - Response of
GET /api/v1/zones/{name}/ds(ADR-0001). - Modify
Zone Request - Request to modify a zone configuration
- Server
Status Response - Server status response
- SoaRecord
- SOA (Start of Authority) record configuration
- Zone
Config - Structured zone configuration
- Zone
Info - Zone information
- Zone
List Response - List of zones response
- Zone
Response - Response from zone operations
- Zone
Status Response - Zone status response: the classic text
detailsplus a typed DNSSEC block parsed fromrndc dnssec -status(ADR-0001).
Constants§
- ZONE_
TYPE_ PRIMARY - Zone type constants
- ZONE_
TYPE_ SECONDARY