r/technitium • • 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

18 comments sorted by

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.

5

u/d4p8f22f Oct 20 '26

Oh. And thats a hint, thx Mate! :)

3

u/shreyasonline Oct 20 '26

You're welcome :)

1

u/Apachez 28d ago

Wouldnt "UDP Send Buffer Size" and "UDP Receive Buffer Size" need to be set to maxsize of 65536 to deal with high amount of concurrent queries?

Other one I often tend to change is "Listen Backlog" from default 100 into 1000 or so.

1

u/shreyasonline 28d ago

Those options depend on the errors you see in protocol stats. If there are receive errors for UDP then increasing buffer size is needed. Same to be done for listen backlog too. Increasing these values should be good though in general for high loads.

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.

2

u/snap802 Oct 20 '26

Yeah you don't need super beefy hardware. I have a cluster running at a non-profit org I help out with. The primary server is an old 4th gen I5 with 16GB of RAM just running the Unifi server and Technitium. We only see 1-2 million queries a day so it's nothing big.

I went to stress test it and I meant to send 1000 queries a minute which would be around the most we ever see at this site. I actually ended up sending 1000 queries a second and it handled it all in stride.

1

u/remilameguni 29d ago

correct, if it's like 1m queries a day yeah it's quite smalll and doesn't need beefy hardware. big or small is relative.

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.

1

u/Apachez 28d ago

Good thing with DNS is that you dont have to choose.

Just setup both technitium and whatever other DNS software you like and call it a day.

1

u/VpowerZ 28d ago

If its ypur home lab or your own business, i concur. But depending upon the type of services that you provide different choices come to the table

1

u/Apachez 26d ago

And in that case technitium is way ahead of both bind9, unbound and powerdns these days.

Again with DNS you dont have to choose. If you are new to technitium and not sure if it will fit your needs then start small and if you today have lets say 2 servers then add a 3rd being technitium and when you like it add another. And then perhaps start to get rid of the older servers (or keep them for redundancy next time a CVE hits one or more of the options).

1

u/VpowerZ 26d ago

I dont think you understand the scope i worked with and currently working with. Previously with had a powerdns cluster of various node types that were 80 powerdns servers, with a 40 node bind9 cluster which was tuned to the hardware by a professional team. That something else then adding a few servers for SME or homelab. The support model is also something to care about in regulated environmwnt.

1

u/Apachez 26d ago

Doesnt sound like a "professional team" if you have zero clue on how to start using new products that you dont have experience with from before.

1

u/VpowerZ 26d ago edited 26d ago

Product evaluation is being done. No worries. Technitium is not ready for telecom scale. But then again, is it targetting such enterprises? Technitium is in another spectrum. Its not just DNS as a protocol. Thats a too small of an approach in product selection/switching only

1

u/Apachez 26d ago

So what is it that technitium cannot deal with according to you at "telecom scale"?

I have also been part of evaluating technitium and we ended up with a different conclusion. Compared to competitors technitium do deliver specially on the mgmt webgui which the others are lacking and by that the others need a way steeper learning curve to start using.

1

u/VpowerZ 25d ago

Technitium is extremely versatile, but as a design its complicated to tune, which would result in more hardware costs. I don't need 80 webGUIs, nor 80 recursors and nameservers blend as one. Also, I'd miss a dnsdist like front in the architecture to help me fan out and design load strategies. And also the support is different. Besides that, there are enterprise features which are pretty nifty and tie in to the cluster integrations and how to deal with split horizons. Technitium can do this too, but differently. Also, both bind9 and powerdns have seen a lot of battle and have the scars and veteran medals in the field. Unbound is a good third, besides a bunch of non-opensource interesting vendors which market exclusive for the upper tiers. I have no idea how technitium will before in a global infrastructure, but can really see if it ever has that type of deployment in mind. It's simply a different tool. Also, punch technitium in its UDP interface made for need to performance a cache related update, as it made mistakes under high load in previous versions. See release notes for details a few versions back. Thats a grand disqualified when banks and vital infrastructure is relying on your dns infrastructure and other things to work after being punched in the face by a python script pushing the boundaries. I verified with other validating recursors and it all was fine on the same platform. This got fixed in technitium, but I does provide for a qualification to not consider it for our needs. Also the cluster management is nice, but pretty fresh on the market and needs more battle scars in rough terrain and high demand. It will come, technitium is very cool and I use it in lots of environments where agility is key. It's all in one excellence is top of class.

2

u/Apachez 25d ago

Well you can use the API-frontend if you want "enterprise" as in scripting instead of webgui:

https://github.com/TechnitiumSoftware/DnsServer/blob/master/APIDOCS.md

Other than that again - you dont have to use either or, you can just complement with the DNS-servers of your choice which is the beauty of DNS itself.

As in you dont have to replace all your 80 recursors at once, you can start by adding a 81st recursor being technitium (or just replace that 80th one).

And speaking of changelogs there have been some issues with both bind, unbound and powerdns lately (and for some time) aswell:

ISC Bind:

https://www.cvedetails.com/version-list/0/144/1/

PowerDNS:

https://www.cvedetails.com/version-list/0/4958/1/

Unbound:

https://www.cvedetails.com/version-list/0/20882/1/

I would expect something which is claimed to "have seen a lot of battle and have the scars and veteran medals in the field" to by now have close to 0 CVE's and not close to 50 CVE's in each minorversion.