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 摘要。