fix(iroh-dns): lower default TXT TTL from 30s to 5s#179
Merged
Conversation
The TTL gates how quickly a restarted connector becomes reachable; control-plane plumbing finishes in <1s but the gateway's resolver serves the stale answer until the TTL expires. Measured on datum-connect (headless tunnel CLI): Restart immediately after stop, TTL=30: ~30s to proxy responding Restart 35s after stop (TTL elapsed): ~1s Refs: datum-cloud/enhancements#756
savme
approved these changes
Jun 10, 2026
Contributor
|
@drewr is there documentation on how this is expected to work and why this change resolves the issue? Feels like this is covering an issue somewhere else in the stack. |
Contributor
Author
|
It centers around the general symptom that a tunnel can take several minutes to provision. Some of that was fixable client-side, but the effect of a long TTL here is reproducible. It shouldn't have downstream effects because nothing else is using Iroh relay TXT records. However, that's not to say that there isn't a better design we could use. |
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.
This is a dramatic improvement to the service by reconverging a tunnel in ~1 second instead of 30+ seconds.
The TTL is the dominant restart bottleneck: control-plane plumbing (heartbeat → reconcile → DNSRecordSet → Envoy metadata) completes in <1s, but iroh-gateway's resolver serves the stale TXT until it expires.
With this change:
Measured on
datum-connect:Cost: a few extra authoritative DNS queries per active endpoint. Negligible at connector-zone cardinality.
Refs: datum-cloud/enhancements#756