Technitium DNS Server. Contribute to TechnitiumSoftware/DnsServer development by creating an account on GitHub.

Description of Change Bugs The code solves two bugs: BUG 1: When trouble shooting a dnsserver with the 'dig' (one of the main DNS troubleshooting tools) the server doesn't answer beca...

Trustworthy expert guide to your Synology NAS.

Powershell commands to display and manage DNS configuration of network interfaces

Technitium DNS Server v15.3 is now available for download. This update adds many new options in Settings, fixes multiple bugs and security issues. See what's new in this release: https://github.com/TechnitiumSoftware/DnsServer/blob/master/CHANGELOG.md

Hello, and thanks for the release. After updating to v15, my two-node Podman cluster fails to be reachable from one another. I've tried many steps including a reinstallation, and found the followin...

Today's GitHub digest: react-native-vision-camera for mobile, DnsServer for privacy, and stop-that-shit to guard AI coding agents. Check out the full list.

CVE ID :CVE-2026-28519 Published : March 15, 2026, 1:36 p.m. | 28 minutes ago Description :arduino-TuyaOpen before version 1.2.1 contains a heap-based buffer overflow vulnerability in the DnsServer component. An attacker on the same local area network who controls the LAN DNS server can send malicious DNS responses to overflow the heap buffer, potentially allowing execution of arbitrary code on affected embedded devices. Severity: 8.8 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

Jede digitale Verbindung beginnt mit einer DNS-Abfrage: DNS fungiert als „Telefonbuch“ des Internets, das Domainnamen in IP-Adressen übersetzt. Fällt DNS aus, können Anwendungen keine Adressen mehr fi...

The vulnerability in BIND DNS server software allowed attackers to crash DNS servers by sending specifically crafted malicious packets.

'You don't have to do more than that to disconnect an entire network' El Reg told as patches emerge

submitted by stratself to selfhosted 27 points | 7 comments https://github.com/TechnitiumSoftware/DnsServer **Technitium DNS Server** (TDNS) has gotten a new release with many awesome features: TOTP authentication, an upgraded .NET library, and many security and performance fixes. But most important of all, it now supports **clustering**. A long-awaited feature, this allows Technitium to sync DNS zones and configurations across multiple nodes, without needing an external orchestrator like Kubernetes, or an out-of-band method to replicate underlying data. For selfhosters, this would enable resilience for many use cases, such as internal homelab adblocks or even selfhosting your public domains. From a discussion with the developer and his sneak peek on Reddit, it is now known that the cluster is set up as a single-primary/multiple-secondary topology. They communicate via good-old REST API calls, and transported via HTTPS for on-the-wire encryption. To sync DNS zones (i.e. domains), the primary server provisions the “catalog” of domains, for secondary ones to dynamically update records in a method known as Zone Transfers. This feature, standardized as Catalog Zones (RFC9432), were actually supported since the previous v13 release as groundwork for the current implementation. As an interesting result, nodes can sync to a cluster’s catalog zone, as well as define their own zones and even employs other catalog zones from outside the cluster. This would allow setups where, for example, some domains are shared between all nodes, and some others only between a subset of servers. To sync the rest of the data such as blocklists, allowlists, and installed apps, the software simply sends over incremental backups to secondaries. The admin UI panel is also revamped to improve multi-node management: it now allows logging in to other cluster nodes, as well as collating some aggregated statistics for the central Dashboard. Lastly, a secondary node can be promoted to primary in case of failures, with signing keys also managed within for a seamless transition of DNSSEC signed zones. More details about configuring clusters is to be provided in a blogpost in the upcoming days. It is important to note that this feature only supports DNS stuff, and not DHCP just yet (Technitium is also a DHCP server). This, along with DHCPv6 and auto-promotion rules for secondaries, is planned for the upcoming major release(s) later on. As a single-person copyleft project, the growth of this absolute gem of a software has been tremendous, and can only get better from here. I personally can’t wait to try it out soon Disclaimer: I’m just a user, not the maintainer of the project. Information here may be updated for correctness and you can repost this to whatever

Wer die Websperren der CUII umgehen will, kann dies direkt bei seinem WLAN-Router FritzBox tun. Wir erklären es euch Schritt für Schritt. Der Artikel <a href="https://tarnkappe.info/tutorials/dns-sperren-umgehen-mit-der-fritzbox-320064.html">DNS-Sperren umgehen mit der FritzBox</a> erschien zuerst auf <a href="https://tarnkappe.info">TARNKAPPE.INFO</a>