{"slug": "technitium-dns-server", "name": "Technitium DNS Server", "category": "networking", "category_name": "Networking and VPN", "description": "", "recommenders": 3, "commenters": 4, "warners": 1, "score": 1.749, "rising": -0.98, "first": "2025-11-27", "latest": "2026-07-26", "why": "I love Technitium DNS and have run it for several years now.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 3, "neutral": 0, "compare": 0, "warn": 1}, "spark": [1, 1, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "I love Technitium DNS and have run it for several years now.", "kind": "", "icon": true, "domain": null, "github_repo": null, "official_url": "https://technitium.com/dns/", "pricing": "", "aliases": ["Technitium DNS Server"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 785041728, "item_id": 49065108, "url": "https://news.ycombinator.com/item?id=49065108", "by": "fastandfearless", "date": "2026-07-26", "version": null, "stance": "recommend", "quote": "It runs Technitium per segment inside Kubernetes via Multus CNI", "excerpt": "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 pl", "context": "", "use_case": "per-segment DNS resolvers", "switched_from": "", "story": "Authoritative Dnsmasq in a MikroTik Container"}, {"id": 737703280, "item_id": 46106455, "url": "https://news.ycombinator.com/item?id=46106455", "by": "feldrim", "date": "2025-12-01", "version": null, "stance": "recommend", "quote": "I am fan of Technitium", "excerpt": "I am fan of Technitium, because I like to build and I built two plugins for it to fit my use case. But at work, we use Windows DNS and Bind in parallel. So, this is also a hobby of mine. The hook for me is that it is built with dotnet, and I have experience in that stack. Other features are secondary actually. I am curious though, what would TDNS do so that you can replace BIND with TDNS in your homelab/workplace or ", "context": "Works where Windows DNS and BIND run in parallel; DNS is a hobby", "use_case": "DNS server", "switched_from": "", "story": "DNS Firewalling with MISP and Technitium DNS Server"}, {"id": 737183040, "item_id": 46073940, "url": "https://news.ycombinator.com/item?id=46073940", "by": "mfro", "date": "2025-11-27", "version": null, "stance": "recommend", "quote": "I love Technitium DNS and have run it for several years now.", "excerpt": "I love Technitium DNS and have run it for several years now. Thanks for the contributions.", "context": "", "use_case": "DNS server", "switched_from": "", "story": "DNS Firewalling with MISP and Technitium DNS Server"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 737473009, "item_id": 46092063, "url": "https://news.ycombinator.com/item?id=46092063", "by": "johnea", "date": "2025-11-29", "version": null, "stance": "warn", "quote": "Technitium seems like another one of those", "excerpt": "I guess wikipedia doesn't agree with you: \"BIND is the de facto standard DNS server\" https://en.wikipedia.org/wiki/Comparison_of_DNS_server_software 9 just being the currently deployed version. A non-wikipedia reference: https://dn.org/a-comprehensive-comparison-of-popular-dns-server-software-bind-knot-powerdns-and-nsd/ Although this article does state that bind's \"configuration files and options require careful atte", "context": "", "use_case": "", "switched_from": "", "story": "DNS Firewalling with MISP and Technitium DNS Server"}]}], "who": [{"by": "feldrim", "context": "Works where Windows DNS and BIND run in parallel; DNS is a hobby", "url": "https://news.ycombinator.com/item?id=46106455", "date": "2025-12-01"}], "tags": [], "use_cases": ["dns server", "per-segment dns resolvers"], "compared": [{"slug": "bind", "name": "BIND", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=46066736", "title": "DNS Firewalling with MISP and Technitium DNS Server", "mentions": 3}, {"url": "https://news.ycombinator.com/item?id=49060339", "title": "Authoritative Dnsmasq in a MikroTik Container", "mentions": 1}], "sentiment_by_month": {"2025-11": {"recommend": 1, "warn": 1}, "2025-12": {"recommend": 1}, "2026-01": {}, "2026-02": {}, "2026-03": {}, "2026-04": {}, "2026-05": {}, "2026-06": {}, "2026-07": {"recommend": 1}, "2026-08": {}, "2026-09": {}, "2026-10": {}}, "versions": [], "version_unnamed": 0, "family_ref": null, "runs_on": null, "lines": [], "quotes": [{"id": 785041728, "item_id": 49065108, "url": "https://news.ycombinator.com/item?id=49065108", "by": "fastandfearless", "date": "2026-07-26", "version": null, "stance": "recommend", "quote": "It runs Technitium per segment inside Kubernetes via Multus CNI", "excerpt": "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 pl", "context": "", "use_case": "per-segment DNS resolvers", "switched_from": "", "story": "Authoritative Dnsmasq in a MikroTik Container"}, {"id": 737703280, "item_id": 46106455, "url": "https://news.ycombinator.com/item?id=46106455", "by": "feldrim", "date": "2025-12-01", "version": null, "stance": "recommend", "quote": "I am fan of Technitium", "excerpt": "I am fan of Technitium, because I like to build and I built two plugins for it to fit my use case. But at work, we use Windows DNS and Bind in parallel. So, this is also a hobby of mine. The hook for me is that it is built with dotnet, and I have experience in that stack. Other features are secondary actually. I am curious though, what would TDNS do so that you can replace BIND with TDNS in your homelab/workplace or ", "context": "Works where Windows DNS and BIND run in parallel; DNS is a hobby", "use_case": "DNS server", "switched_from": "", "story": "DNS Firewalling with MISP and Technitium DNS Server"}, {"id": 737473009, "item_id": 46092063, "url": "https://news.ycombinator.com/item?id=46092063", "by": "johnea", "date": "2025-11-29", "version": null, "stance": "warn", "quote": "Technitium seems like another one of those", "excerpt": "I guess wikipedia doesn't agree with you: \"BIND is the de facto standard DNS server\" https://en.wikipedia.org/wiki/Comparison_of_DNS_server_software 9 just being the currently deployed version. A non-wikipedia reference: https://dn.org/a-comprehensive-comparison-of-popular-dns-server-software-bind-knot-powerdns-and-nsd/ Although this article does state that bind's \"configuration files and options require careful atte", "context": "", "use_case": "", "switched_from": "", "story": "DNS Firewalling with MISP and Technitium DNS Server"}, {"id": 737183040, "item_id": 46073940, "url": "https://news.ycombinator.com/item?id=46073940", "by": "mfro", "date": "2025-11-27", "version": null, "stance": "recommend", "quote": "I love Technitium DNS and have run it for several years now.", "excerpt": "I love Technitium DNS and have run it for several years now. Thanks for the contributions.", "context": "", "use_case": "DNS server", "switched_from": "", "story": "DNS Firewalling with MISP and Technitium DNS Server"}]}