Repository navigation
route53: ZoneClass negativeCacheTTLSeconds owns the hosted zone SOA MINIMUM - #23
Merged
Merged
Conversation
…INIMUM Resolvers cache NXDOMAIN/NODATA for the SOA MINIMUM (RFC 2308); Route 53 creates zones with 86400, so records written by dns-api can stay invisible to in-VPC resolvers for a day. The Route 53 ZoneClass parameter negativeCacheTTLSeconds makes the controller converge the apex SOA MINIMUM of created and adopted hosted zones (one read per reconcile, one UPSERT changing only MINIMUM, tracked as a pending hosted-zone change NegativeCacheTTL). The observed MINIMUM is published in zone status data.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Resolvers cache NXDOMAIN/NODATA for the zone SOA MINIMUM (RFC 2308). Route 53 creates zones with MINIMUM 86400, so a record written by dns-api after a consumer's first lookup can stay invisible to in-VPC resolvers for a day. Platform worked around this with a CoreDNS forward hack; the zone's negative-cache TTL is dns-api's to own because it is the only writer of the zone.
What
Route53ZoneClassParameters.negativeCacheTTLSeconds(int32, 0..2147483647, optional). Absent = SOA untouched.PendingHostedZoneChange.Operation=NegativeCacheTTLthrough the existing INSYNC barrier.Route53ZoneStatusData.negativeCacheTTLSeconds: observed MINIMUM.docs/design/route53-provider.md), README.Checks
task generate,controller-chart:sync-crds,controller-chart:lintgo test ./internal/go/providers/route53/... ./pkg/go/api/route53/...,go build ./...Consumer: appthrust/platform invert-wlc A2 (PMC CoreDNS takeover drops the forward hack).