coocood/geodns — explained in plain English
Analysis updated 2026-07-17 · repo last pushed 2018-10-30
Direct users to the geographically nearest server for a multi-region service.
Split traffic between servers using weighted DNS responses.
Run a global service like an NTP time server pool with location-aware DNS.
Monitor DNS query performance through the built-in HTTP metrics interface.
| coocood/geodns | aeneasr/github-trends | n8n-io/n8n-sandbox-service | |
|---|---|---|---|
| Stars | 4 | 4 | 4 |
| Language | Go | Go | Go |
| Last pushed | 2018-10-30 | 2020-12-18 | 2026-06-15 |
| Maintenance | Dormant | Dormant | Maintained |
| Setup difficulty | hard | easy | hard |
| Complexity | 4/5 | 2/5 | 4/5 |
| Audience | ops devops | pm founder | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Extensive testing has only been done on single-CPU configurations, per the README.
A Go-based DNS server that answers domain lookups differently based on the requester's location, routing users to the nearest server.
Mainly Go. The stack also includes Go, DNS, JSON.
Dormant — no commits in 2+ years (last push 2018-10-30).
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
double-check against the repo, no cap.