Following extensive stress-testing, we have officially moved the production backend of AdGuardHome-Edge to the latest upstream base. This synchronizes our project with critical fixes deployed by the AdGuardTeam, most notably a critical correctness bug in the DNSSEC caching layer (PR #434). In the stock version, queries with and without the DO-bit (DNSSEC OK) could erroneously share cache slots, leading to stripped security signatures for validating clients. Our edge deployment permanently fixes this.
During the migration, our custom Zero-Alloc UDP network engine was successfully rebased and verified under peak load. To maintain strict engineering hygiene, we have completely refactored our internal git history, pruning legacy upstream branches and establishing a clean, dedicated deployment structure. The server continues to operate with a zero-allocation profile on the hot UDP path, combining absolute data correctness with extreme microsecond-level throughput.
We have successfully migrated our custom network engine to the fresh v0.81.4 base, incorporating critical upstream DNSSEC cache fixes into our optimized stack.
Highlights
- Migrated to upstream v0.81.4 codebase with complete feature parity
- Incorporated PR #434 fixing DNSSEC DO-bit cache key collisions
- Clean rebase of our custom Zero-Alloc UDP packet processing pipeline
- Full internal repository refactoring and tag modernization
- Verified production stability under real-world multi-client workloads