~cameri/blog > _

/posts/technitium-dns.md

Technitium DNS

Not long ago I switched to using AdGuard Home for my DNS needs, as documented in a previous blog post. While AdGuard Home has served me well, I recently came across Technitium DNS and decided to give it a try.

The installation process was straightforward, and I was able to get it up and running quickly. The web interface is user-friendly, making it easy to configure settings and manage my DNS records.

I was drawn to Technitium DNS because of it's clustering capabilities, which allow for multiple instances to share the same configuration and data and sync almost instantly. This was a feature that both Pi-hole and AdGuard Home lacked, resulting in me having to manually replicate changes across multiple instances or set up third-party syncing solutions like AdGuardHome-Sync.

After using Technitium DNS for a few weeks, I can confidently say that I'm impressed with its performance and features. While the clustering capability was my primary reason for switching, I've also noticed that Technitium DNS is more responsive and uses less memory compared to AdGuard Home.

When I had AdGuard Home running it constantly had heavy memory usage during syncing, when querying for logs, and sometimes just during normal operation. Troubleshooting a blocked DNS query was a pain due to the slow interface.

Fortunately, I found out about Technitium DNS right before the holidays, so I was able to set it up and migrate my settings (manually) over without any downtime.