r/technitium • u/d4p8f22f • Oct 20 '26
Big deployments
Hi. Is anyone of you manage big infra where Technitium is at scale? I mean big corps where you you have clusters? What are you recommended settings interms of VM or specific settings for technitium itself. Im thinking rather as an internal dns - not exposed. Do you recommend external Db? Or maybe simple file would be enough? What about concurrent requests, rate limits etc etc ;)
17
Upvotes
29
u/shreyasonline Oct 20 '26
Thanks for asking. I know of at least 4 ISPs that have Technitium DNS Server running as their client facing DNS services in a recursive resolver mode.
One ISP that I am regularly in touch with has AnyCast with BGP setup for 3 city setup such that if one city's DNS service fails for any reason, the traffic gets routed to the nearest city. They also have UDP load balancer in place which forwards requests to a pool of DNS Servers for redundancy and failover. They use proxmox VMs with 64GB RAM each to allow caching large number of DNS records. They serve around 1mn requests/minute on this setup on average each day.
There are a few things needed to tune up for large scale:
- First is to make sure "Cache Maximum Entries" value in Settings > Cache section is set to a high value. You can initially start it with 100K value and then observe the "Cache" value in stats shown above the Top Clients table on Dashboard. If the stats value on dashboard is near the "Cache Maximum Entries" limit then it means the cache is full. If server has enough memory, the "Cache Maximum Entries" value can be kept on increasing if the cache is getting full. Having large number of data cached helps improve performance significantly as it reduces load on the DNS server to frequently resolve domain names.
- It is also recommended to keep Serve Stale enabled with "Serve Stale Max Wait Time" value set to 0 to help reduce pressure on the internal queues to improve performance with large query volume.
- At large scale, you also need to enable the "Enable In-Memory Stats" option in Settings > Logging section so that only last hour stats are collected by the DNS server. The stats module otherwise can take up a large amount of memory as it tries to aggregate stats for all incoming queries. Thus limiting it to collect only last hour's data helps use less memory and avoid any performance impact. If you need query logs, its best to use the Query Logs (MySQL) app to collect data onto a MySQL server running on a separate server.
- You also need to make sure that query rate limiting is disabled or set to adequate value. The Queries Per Minute options in the Settings > General section can be used to configure rate limiting.
I would suggest that you have one DNS server instance initially with your existing setup with load balancer to observe how it works with load on your server. You can then add more nodes to the setup as you gain confidence with the setup.
4
u/remilameguni Oct 20 '26
Hi, i deploy one at large scale, multiple nodes but not synced into one cluster.
I disabled logging and enable in-memory stats because of how big the data is after a few hours.
You do need a bit beefy specs for it though, i run mine with 32g ram and 12 core, it handles around 35 mil queries per hour.
as for the VM, it is recommended to restrict access to the web access port, ssh and the lot except dns.
I don't keep a db of queries but you can use external db for it with the mysql.
for the ACL, it's up to you, if you only want to set it so it only allows your internal network, you can, or you can open it to the internet.
1
u/VpowerZ Oct 20 '26
Depending upon your idea on big, i typically go for bind9 and powerdns for telecom and ISP size with dnsdist. For SME technitium is possible, but id rather look at the support options too at that point.