-
Notifications
You must be signed in to change notification settings - Fork 4
chore: change DNS record TTL from 10 minutes to 2 seconds #70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
// Coder: We've changed this from 10 minutes to 2 seconds, as we'd like to use | ||
// the existence of Coder Connect DNS records to determine whether Coder Connect | ||
// is running. | ||
const defaultTTL = 2 * time.Second |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
10 seconds sounds better to me. The only time that records will conflict will be during a restart of a workspace, which I would guess takes 20-30 seconds in the fastest possible template.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We aren't just worried about records with conflicting IP addresses, we are worried about turning off Coder Connect entirely and then using some other tool to connect to the workspace, and having the OS return a stale record indicating that Coder Connect is running when it isn't.
So, the relevant time scale is how quickly a human can turn off Coder Connect and then switch to another tool, not a workspace restart.
Relates to coder/internal#466 Brings in coder/tailscale#70
Relates to coder/internal#466
This modifies the TTL of all DNS records programmed into the DNS resolver.
I've tested this by running Coder Desktop macOS against a fresh dylib: