Roadmap
dcm is under active, heavy development and far from feature-complete; existing behaviour may still change. The authoritative list of what is being worked on is the issue tracker — this page is the shape of it.
-
Auth:
inc/auth.phpis a stub — always passes. Add HTTP Basic Auth or session login when external access is needed. -
Compressed logs:
.log.2.gzand older not yet analyzed — addzcatsupport for longer time ranges. - Notification history (phase 2): the bell reflects live state only; persist faults/events (unreachable node, lost upstream, with timestamps) in SQLite, fed by a periodic background check.
- Theming: a Skin/Style page to pick light/dark palettes and custom accent colours, built on the existing CSS variables and stored in SQLite.
-
Ad-blocking lists: subscribed block lists with a scheduled update, separate from the
isolatedhosts file. - DHCP / DHCPv6 and TFTP / PXE boot: dnsmasq does all of it, dcm does not expose it yet — see the deferred sections of the Directive catalog.
- Multi-network / split-horizon DNS: answering the same name differently per network.
-
Encrypted upstream DNS and DNSSEC: the design space is explored in Encrypted upstream DNS; dcm manages only the
server=pointer today. - VM network auto-detection: the one-click subnet relocation in Hosts files is an interim solution.
Phase 1 is a DNS resolver and forwarder. Everything else — DHCP, TFTP/PXE, ad-block lists, authoritative zones — gets its own catalog section when the feature is built, and is gated per node by what that node's dnsmasq build actually accepts.
