irinesistiana/mosdns

一个 DNS 转发器

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 57 minutes ago
Added to GitGenius on September 18th, 2026
Created on November 26th, 2020
Open Issues & Pull Requests: 118 (+0)
GitHub issues: Enabled
Number of forks: 486
Total Stargazers: 3,746 (+0)
Total Subscribers: 28 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.1 days
Mean response time: 24.5 days
90th percentile: 52.0 days
Tracked items: 53

Most active contributors

Sign in to see contributor activity.

How this project is maintained

98% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 54% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 53
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 636 days
Stale 30+ days: 52
Stale 90+ days: 51

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • F&Q (1)

Detailed Description

mosdns is a DNS forwarder that handles DNS queries and routes them according to configurable rules.

The tool addresses the need to intercept and intelligently route DNS traffic, particularly useful in environments where different queries should be resolved by different upstream servers or where DNS responses need filtering or modification. mosdns accepts DNS queries over multiple protocols—including standard UDP/TCP, DNS-over-HTTPS, DNS-over-TLS, and DNS-over-QUIC—and forwards them based on user-defined rules. This multi-protocol support allows it to work in restricted network environments and provides flexibility in how clients connect to it.

mosdns suits operators who need fine-grained control over DNS resolution routing, such as those managing networks with split-horizon DNS requirements, content filtering needs, or hybrid setups combining multiple DNS providers. It is particularly valuable for users in regions with DNS censorship or those wanting to route queries selectively to different resolvers based on domain patterns. The project is written in Go, making it lightweight and easy to deploy across different platforms.

Development activity shows consistent engagement with the codebase through regular commits addressing bug fixes and feature additions. The project maintains active issue triage, responding to user reports and feature requests. Documentation is centralized in an external wiki rather than the repository itself, indicating a structured approach to maintaining separate concerns between code and user guidance. Docker images are actively published and maintained, reflecting attention to deployment accessibility.