AdguardTeam / AdguardTeam/dnsproxy
Please document how upstream and fallback work
- Linguagem predominante
- Go
- Estrelas
- 3.3k
- Forks
- 343
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
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?
Guia de contribuição
Nenhum guia de contribuição indexado para este repositório
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- go
- Domínio
- documentation, networking
- Tipo de issue
- Documentação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Estagnada
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 35/100