Habr•October 31, 2026•🇷🇺Translated from Russian

Building Resilient DoH Failover on MikroTik RouterOS to Handle Unreachable Cloudflare Responses

A branch office network suddenly stopped loading certain pages such as the Tailwind CSS CDN build that had worked reliably for weeks, while the rest of the internet remained accessible. Investigation on the MikroTik router revealed that :resolve returned valid addresses, DoH responded with Status:0, and the health monitor reported the upstream as healthy, yet clients experienced timeouts.

The root cause was two specific IP addresses returned by Cloudflare: 8.6.112.0 and 8.47.69.0. These were legitimate responses, but no route existed from the affected network segment to those prefixes. Standard resolver health checks that only verify whether an IP was received cannot detect this class of failure.

Initial DoH Deployment and Its Limitations

By default, RouterOS routes local DNS queries in plaintext toward the provider. Enabling DoH required a single command: /ip dns set use-doh-server=... verify-doh-cert=yes. The administrator selected the Cloudflare Family filtering resolver and initially considered the task complete.

Within days, reports arrived from the branch. Disabling DoH and testing plain DNS produced identical addresses, confirming the issue was not filtering but reachability. Client-side verification using curl --resolve demonstrated that the same IP worked from the main gateway yet timed out from the branch.

Requirements and RouterOS Constraints

The administrator defined three core requirements: all router-to-upstream traffic must use HTTPS with certificate validation, local clients must be forced through the router resolver, and automatic failover to a secondary DoH endpoint must occur on failure with automatic return on recovery.

RouterOS natively supports only one active DoH upstream. The often-recommended /ip dns static-server type=doh syntax does not exist in current versions. Bootstrap servers listed under servers= are used solely for initial name resolution of the DoH hostname and are not treated as fallback resolvers when DoH fails.

Health Monitor Evolution and Key Fixes

  • Version 0.1.0 incorrectly accepted any IP-typed response, including the unreachable Cloudflare pair.
  • Version 0.2.0 introduced content validation against known stub prefixes and switched to out-of-band HTTPS JSON probes to avoid disrupting active DoH sessions.
  • Later versions added dual-threshold logic (failureThreshold=2, recoveryThreshold=2) to implement hysteresis and prevent flapping.
  • Clock validation rejects dates outside 2025-2035 because an invalid system time breaks certificate verification and mimics upstream failure.

Static DNS entries were added for both primary and secondary DoH hostnames plus dns.google bootstrap addresses to break circular dependencies. The trust anchor SSL.com TLS ECC Root CA 2022 had to be imported because the built-in trust store does not cover the Cloudflare chain.

Current Architecture

The production configuration maintains four ordered stages: primary DoH, secondary DoH, optional tertiary DoH, and optional plain DNS as last resort. Only one stage is active at any time due to RouterOS limitations. The monitor script stores state in global variables, logs only on transitions, and performs pre-switch validation of the candidate endpoint plus post-switch verification before finalizing the change.

Testing confirmed that route injection or static hostname-to-reachable-IP mappings were the only effective remedies; merely changing the resolver brand never resolved the unreachable-prefix problem.

Related articles

AntiMalware•Other

Yandex Tests Compass Device for Taxi Navigation During GPS Outages

Yandex is conducting trials of a compact Compass device in 10,000 taxis connected to its service to maintain accurate vehicle positioning when GPS signals are lost or jammed. The device connects to the OBD diagnostic port and pulls wheel speed data via the CAN bus while using its built-in gyroscope and accelerometer to determine direction of travel. These readings are sent over Bluetooth to the Yandex Pro driver app, which combines them with the last known GPS coordinates and frequent Wi-Fi access point scans to update the map in real time. The initiative addresses ongoing navigation problems that have affected Russian cities since spring 2022 and have been compounded by regular mobile internet outages since spring 2025. Earlier, Yandex tested a similar OBD-connected gadget called Yandex Pathfinder in 2023. The company has not disclosed timelines for completing the current trial or rolling the solution out more widely, though it plans to make Compass available to ordinary drivers later. Yandex navigation apps have also offered an offline step-by-step routing mode since 2025.

Habr•Other

Apple Attributes Widespread Service Outage to Faulty Internal IT Update

Apple has confirmed that the large-scale outage affecting its systems and user services on November 17, 2026, was caused by an incorrect internal update within the company's IT infrastructure. The incident impacted multiple consumer-facing services including the App Store, iCloud, Apple Pay, and Apple ID authentication. Users reported inability to download applications, sign in to accounts, or activate devices during the disruption. Internal corporate tools such as AppleWeb, AppleConnect, employee VPN access, corporate calendars, and the internal incident-tracking site were also taken offline. Retail operations in Apple Stores worldwide experienced interruptions to sales, repairs, and customer service processes. Company engineers restored most systems within four hours and stated they were working to return remaining services to normal operation as quickly as possible. Apple explicitly ruled out any external cyberattack or third-party interference as the cause of the outage.

Habr•Other

Global Outage Disrupts Apple Services Including App Store, iCloud and Apple Pay

On November 17, 2026, widespread disruptions affected multiple Apple services worldwide, including the App Store, iCloud, Apple Pay, and Apple ID authentication systems. The incident impacted users attempting to download applications on iPhone devices, sign into accounts, or activate new hardware. Apple confirmed problems with Apple Music and App Store functionality, along with performance degradation or complete unavailability of iCloud for all users. The outage was explicitly stated as unrelated to any country-level internet traffic filtering or restrictions. Service interruptions prevented normal operation of cloud storage, music streaming, and payment processing features tied to Apple ID. No official timeline for full restoration was provided in the initial reports from the company.

Habr•Other

Forbidden Fruit: Recovering Delisted iOS Apps Wirelessly via Reverse-Engineered Apple Protocols

A detailed technical investigation demonstrates how to restore delisted applications to iOS and iPadOS devices directly on the target hardware without cables, computers, or Apple-signed developer certificates. Researchers performed extensive reverse engineering of Apple binaries including Configurator, CoreADI, AuthKit, AppleMediaServices, and legacy FairPlay components to replicate cryptographic device provisioning and authentication flows in pure Go. The work reconstructs ADI provisioning for both IdMS and AMD states, SRP-based GrandSlam authentication, SAP envelope signing, and white-box AES transformations previously executed only inside Apple binaries. All steps were validated on iOS 17.3.1 through 18.2.1 and iPadOS 18.7.1, enabling a single-device workflow that obtains purchase history, downloads .ipa files, and installs them via a custom server recognized by the system installer. The resulting implementation eliminates dependencies on macOS drivers, iTunes, Unicorn emulation, and closed-source libraries while remaining cross-platform.