Skip to content

Rework DNS resolving#216

Merged
Snawoot merged 4 commits into
masterfrom
bump_def_dns_cache_ttl
May 14, 2026
Merged

Rework DNS resolving#216
Snawoot merged 4 commits into
masterfrom
bump_def_dns_cache_ttl

Conversation

@Snawoot
Copy link
Copy Markdown
Member

@Snawoot Snawoot commented May 14, 2026

Purpose of proposed changes

  • Fix inconsistencies regarding DNS cache: now (potential) resolves of both requested hosts and upstream proxies are done the same way, using same DNS cache.
  • Bump default DNS cache time to 10 seconds, effectively enabling it by default. It should reduce strain on upstream forwarders such as home gateways which may refuse repeated queries for the same name.
  • Allow resolving of upstream proxy name also be private.
  • Simplify code and logic.

Essential steps taken

  • Introduce forced DNS resolving before and after chain of proxy and filter dialers.
  • Unify DNS resolution caching in the same caching resolver rather than having it inside separate caching resolving dialer.

@Snawoot Snawoot self-assigned this May 14, 2026
@Snawoot Snawoot merged commit 9d983f1 into master May 14, 2026
@Snawoot Snawoot deleted the bump_def_dns_cache_ttl branch May 14, 2026 23:28
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.

1 participant