New website!
We're excited to announce the launch of our new website! It features a fresh design, improved navigation, and more information about our services.
New status page!
Ever wanted to know the status of all our DNS servers? Well now you can!
I've created a new status page to show the status of all our DNS servers, and potential maintenance that would be performed.
You can view this at Here!
New easy configure tool now live on the website!!
I'm happy to announce the new tool to allow easy configuration of clients.
It's now live under the client configuration section. Give it a try!
Asia server now open to the public!!!
I'm happy to announce the Asia server is now public.
After a lot of consideration this was the next place to go.
Possible Asia server soon??? We'll see...
Also happy new years! And may Tri-DNS continue through 2025.
DoQ instability reason found, no. Now fixed! (maybe)
The issue has been fixed, it was a issue with Technitium DNS server, and their DoQ service.
The issue should now be fixed, though this fix was just rolled out so do still keep DoT / DoH as a backup just in case.
Until I do further testing to confirm its 100% safe to use.
(If you want to read the original post see git commit 248c597 on the tri-dns-web repo.)
DNS-over-QUIC instability.
It seems that DNS-over-QUIC is still unstable. It could be anything, Dependencies, Debian 12 related issues, or just the backbone software itself.
Anyways, I generally recommend staying AWAY from DoQ, and use Dns-over-https/3 if you want the benefits of DoQ.
I'll do another update post when / if DoQ ever gets a fix.
Tri-DNS now has a dedicated privacy page.
I believe in being as transparent as possible in what Tri-DNS does, and doesn't log, in a simple manner that is easy to understand. Instead of a 5 page essay like most privacy policies, with complex terms that only a dedicated privacy nerd could understand, or lawyer.
You can find info: here
tri-dns.net and eu.tri-dns.net now redirect to the main website.
Due to search engines indexing tri-dns.net and putting it near the top, I've made both domains redirect to the main one.
DNSSEC REENABLED ACROSS ALL REGIONS!
Due to past issues with DNSSEC it was temporarily disabled on all nodes, it was reenabled on Europe as a test ground on 12/1/24.
It has since been reenabled on the North American Node after extensive testing on the less popular EU node.
IMPORTANT!
DoQ, DoH/3 (And DoH) seemed to have been fixed by me tinkering around, working on fixes for the past few days, one of the fixes tested seems to have worked*.
Using these protocols should be safe now, though I do still recommend at least having 1 DoT service as a backup, as that one seems to work no matter what.
Fixed Ipv6 in NA node, issue was caused by a misconfigured network, caused by me not reading digitaloceans documentation.