Skip to content

Conversation

@Evrard-Nil
Copy link
Contributor

No description provided.

@Evrard-Nil Evrard-Nil force-pushed the fix-gateway-dns-cache branch from 9e9b3de to 54a86be Compare November 21, 2025 02:26
@kvinwang
Copy link
Collaborator

Hardcoding google DNS seems unreasonable—users should be able to choose their preferred DNS server.
I'm curious about what's the root cause of the 30-minute cache issue.

@Leechael
Copy link
Collaborator

@Evrard-Nil Since dstack inherits the DNS resolver from systemd, do you think we can fix this by configuring systemd-resolved instead of forcing it to use a single DNS resolver? It's more like introducing another single point of failure.

@kvinwang
Copy link
Collaborator

Certbot simply waits for a fixed time (configurable via --dns-xxx-propagation-seconds), and there was a discussion on adding active polling. A better fallback approach would be adding a similar configuration parameter MAX_DNS_WAIT_SECONDS to cap the total duration of DNS active polling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants