DNS Resolver Operator Discovers Missing DNSSEC Validation After Six Months via External Test
A solo developer operating VantageDNS, a recursive DNS resolver with content filtering, discovered that DNSSEC validation had been completely disabled for six months. The issue came to light only after running the public DNS-OARC test suite, not through any internal monitoring alerts.
External Test Reveals Critical Gap
The DNS-OARC cmdns test sends dozens of queries with randomized names and checks port randomization, DNS ID entropy, TCP support, IPv6, QNAME minimization, and DNSSEC behavior. Five checks passed with green results, but one line appeared in red: "Lookup succeeded while signature was invalid." Manual verification with dig against dnssec-failed.org confirmed the resolver returned NOERROR and a valid answer instead of the required SERVFAIL status.
Why Passive Monitoring Failed
Existing health checks, latency metrics, and cache-hit-rate alerts could not detect the missing validation. When DNSSEC checking is disabled, the resolver answers faster, returns more successful responses, and appears completely healthy. The only reliable detection method is an active probe that deliberately supplies an invalid signature and verifies rejection.
Configuration History and Technical Debt
The cause was a comment left in the Unbound configuration during the MVP stage:
- DNSSEC validation — disabled in MVP, add in Sprint 5
- Requires auto-trust-anchor-file + root.key, which is absent by default
Subsequent sprints passed without addressing the item. A separate Go-based DNSSEC validator existed but was bypassed because production recursion was handled by an Unbound sidecar that forwarded traffic without validation.
Enabling Validation and Crash-Loop
Initial attempts to enable validation using auto-trust-anchor-file caused a permission-denied error inside the chroot environment because Unbound (running as _unbound) needed write access to the directory to perform RFC 5011 key-rollover updates. The container entered a crash-loop until the configuration was switched to a static trust-anchor-file pointing to a pre-generated root.key.
Verification Steps and Performance Impact
After the change, the operator established a repeatable verification checklist:
- dnssec-failed.org and sigfail.verteiltesysteme.net must consistently return SERVFAIL
- Signed domains must return the ad (authenticated data) flag
- Popular domains must resolve identically to results from 1.1.1.1 and 8.8.8.8
Latency measurements showed no measurable penalty: cold-cache queries to signed zones averaged 24 ms versus 28 ms for unsigned zones. Memory usage remained around 25 MB.
The operator now runs periodic active checks against dnssec-failed.org and recommends that anyone operating a resolver perform the same DNS-OARC test immediately.
Related articles
Cloud4U Webinar Details Migration to On-Premises Microsoft Exchange Server Including Email, Calendars and Infrastructure Setup
Cloud4U is hosting a webinar on November 20 at 12:00 MSK focused on migrating corporate email systems to a self-hosted Microsoft Exchange server. The session covers end-to-end planning from initial preparation and pilot testing through full data transfer and final cutover. Participants will learn practical methods for moving messages and calendars while maintaining delivery reliability and avoiding spam folder placement. Specific tools such as imapsync and PST files are examined along with strategies for handling duplicate messages during repeated sync passes. The webinar also addresses why simply updating MX records is insufficient and explains the correct configuration of SPF, DKIM and DMARC records. Additional topics include calendar migration via ICS files, limitations with active meetings, and post-migration verification steps before decommissioning the legacy system.
MTS Expands Global Access Service to Most Tariffs for ChatGPT, Netflix and Other Foreign Platforms
MTS has broadened availability of its Global Access service, which enables subscribers to reach ChatGPT, Claude, Netflix, Spotify and similar overseas platforms without using a VPN. The option is now offered on the majority of current and archived tariff plans, with the exception of Membrana, MTS Junior and MTS Junior+. It remains incompatible with Membrana, Safe Childhood and Safe Internet add-ons. Global Access functions exclusively over the MTS mobile network and requires no additional applications. Supported platforms also include Strava and Ticketmaster. The service is positioned for resources unavailable in Russia but not blocked by Roskomnadzor. New users receive seven free days, after which the monthly fee is 249 rubles, while TOP and TOP+ tariffs include it at no extra cost.
Yandex Restores Access to 99.55% of Yandex Disk User Data After Service Disruption
Yandex has restored access to 99.55% of user data stored on Yandex Disk following a major service outage. Core functions including automatic photo uploads from smartphones, downloading files and folders as archives, and video playback have been returned to normal operation. The company stated that recovery work is still underway and that inaccessible files do not necessarily mean permanent data loss. Users experiencing issues with specific files are advised to contact Yandex Disk technical support. Yandex is also redistributing computing resources across additional locations in various Russian regions to improve stability and fault tolerance. The number of these locations continues to grow, although no timeline has been provided for full restoration of the remaining data.
Survey Shows 42% of Organizations Unify Multi-Vendor Security Tools into Single Protection Contour
A live AM Live broadcast on cybersecurity ecosystems revealed that 42% of participants have already combined solutions from multiple vendors into one unified security contour. Another 23% reported partial integration of tools, while 24% keep their protections operating independently and only 11% rely exclusively on a single vendor. Panelists emphasized the need for clear responsibility assignment, seamless data exchange, and formation of shared security context across products. Key selection criteria for ecosystems included breadth of product lines for 32% of viewers and discounts or bonuses for 28%. Experts advised practical testing of interoperability and evaluation of total cost of ownership before committing to any model. Service provider responsibilities for integration, SLA compliance, and outcomes must be defined in advance, according to CURATOR director Edgar Mikaelyan. After the session, 32% of attendees stated plans to launch or expand a security ecosystem project.