It runs Technitium per segment inside Kubernetes via Multus CNI (though K8s isn't strictly required and could be stripped out).
I'm currently planning to join it with another project of mine, ovn-fabric (https://github.com/mabels/ovn-fabric), which handles declarative OVN/OVS topology and uses transit networks/namespaces to treat things like WireGuard or ZeroTier as virtual uplinks—DN42 is next on the list for that as well.
Comments
Nice work! I ran into that exact same MikroTik limitation when trying to set up segment-based DNS resolvers and forwarders for per-region routing.
After a lot of procrastination, I ended up taking a different path to solve it: https://github.com/mabels/unified-dns-dhcp-chart
It runs Technitium per segment inside Kubernetes via Multus CNI (though K8s isn't strictly required and could be stripped out).
I'm currently planning to join it with another project of mine, ovn-fabric (https://github.com/mabels/ovn-fabric), which handles declarative OVN/OVS topology and uses transit networks/namespaces to treat things like WireGuard or ZeroTier as virtual uplinks—DN42 is next on the list for that as well.