AdguardTeam / AdguardTeam/dnsproxy

Please document how upstream and fallback work

未关闭
#179 2 条评论 7 个 reaction 已指派 0 人 在 GitHub 查看
documentation enhancement
主要语言
Go
星标
3.3k
派生
343
PR 合并指标
30 天内没有已合并 PR

描述

1. How are upstream servers used? Random, round-robin, fastest ... (`--all-servers` is clear)

2. What does upstream not available mean? dnsproxy cannot connect to the server, or it can but gets back a DNS error?

3. When the upstreams are not available, how are the fallback servers used? In order, random, ...

4. Does dnsproxy monitor the upstream servers and switches back to them from fallkback, when available again?

贡献指南

这个仓库没有索引到贡献指南

调研方向

No files, tests, or entry points are named. Start by locating the code that selects upstream and fallback DNS servers, then trace how unavailable servers and recovery are handled. Done means documenting selection order, failure semantics, fallback behavior, and switching back to upstreams when they recover.

由索引模型根据 Issue 内容生成。

评估

技术栈
go
领域
documentation, networking
Issue 类型
文档
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
基本清楚
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。