How syedwafeeq/dns-resolver-implementation works
DNS Consensus Resolver accepts DNS-over-UDP queries, checks its TTL cache, and on a miss queries Google and Cloudflare over DoH. It extracts A records, resolves ASNs, and validates private-address, IP-overlap, and ASN-overlap signals before returning the Google response or a sinkhole answer. Transactions are queued for JSON-line logging. The implementation is concentrated in resolve.py; README documents the capabilities and flow. No separate source module or persistent cache implementation is present.
Main entry points: resolve.py Query Handler
Components 13
DNS Server
- UDP Listener
resolve.py - Query Handler
resolve.py - Sinkhole Reply
resolve.py
Consensus Validation
- Google DoH
- Cloudflare DoH
- A Record Extraction
resolve.py - ASN Lookup
resolve.py - Response Validator
resolve.py
Cache and Logging
- TTL Cache
resolve.py - Log Queue and Writer
resolve.py - JSON Log File
resolve.py
Other components
- DNS Client
- RDAP Service
Connections 14
- DNS Client → UDP Listener: sends DNS
README.md - UDP Listener → Query Handler: dispatches query
resolve.py - Query Handler → TTL Cache: checks cache
resolve.py - Query Handler → Google DoH: queries DoH
resolve.py - Query Handler → Cloudflare DoH: queries DoH
resolve.py - Query Handler → A Record Extraction: extracts records
resolve.py - Query Handler → ASN Lookup: gets ASN sets
resolve.py - ASN Lookup → RDAP Service: looks up ASN
resolve.py - Query Handler → Response Validator: checks consensus
resolve.py - Query Handler → Sinkhole Reply: builds blocked reply
resolve.py - Query Handler → TTL Cache: stores response
resolve.py - Query Handler → DNS Client: sends DNS reply
resolve.py - Query Handler → Log Queue and Writer: queues event
resolve.py - Log Queue and Writer → JSON Log File: appends JSON
resolve.py