Skip to content

Backlog

DNSao is stable for daily use, but there are several intermediate improvements planned. The focus is on making the resolver easier to operate, easier to understand, and more useful for LAN and homelab deployments.

Improve Dashboard Observability

The dashboard should continue evolving from a summary page into an operational view of the DNS server.

Planned areas:

  • DNS server queue and backpressure stats
  • UDP, TCP, and HTTP query counts separated by protocol
  • Upstream timeout and error rates per resolver
  • Cache size, eviction count, and hit-rate trends
  • Rewarm success and failure counts
  • Current upstream health and last-seen status

Local DNS Improvements

Local mappings are useful for homelabs and internal services. The goal is to make this area more flexible while keeping the configuration simple.

Planned areas:

  • Support for local AAAA records
  • Support for additional local record types where they make sense
  • CNAME-style local aliases
  • Better examples for homelab naming patterns
  • Optional import of local mappings from a separate file

Blocklist Management Improvements

Blocklists and allowlists should be easier to inspect and troubleshoot from DNSao itself.

Planned areas:

  • Show list download status in the dashboard
  • Show last refresh time and loaded-domain count per list
  • Make failed list downloads visible in the dashboard
  • Support local file blocklists and allowlists
  • Support per-list enable/disable controls
  • Add list syntax validation and reporting

Packaging and Deployment Polish

DNSao should be easy to run on common small-server setups without requiring users to assemble deployment details from scratch.

Planned areas:

  • Publish example Compose files for common profiles such as privacy, balanced, and udp-only
  • Add systemd hardening documentation
  • Add upgrade and rollback guidance
  • Add sample firewall rules
  • Add low-memory and Raspberry Pi deployment guidance