Designing and Implementing Private Cloud Security Across Geographically Distributed Data Centers
In this article the author shares practical experience in designing and implementing protection for a private cloud hosted across two geographically separated sites of a data center (ЦОД).
The material does not contain deep technical details but instead describes the path from an assumed ideal solution to real-world implementation through research, errors, technical constraints, and necessary compromises.
Background and Objectives
The task appeared fairly standard: ensure service resilience, achieve compliance with information security requirements, and preserve normal manageability of the infrastructure.
On paper such projects usually look like combinations of best practices: high availability, segmentation, NGFW, some dynamic routing, and it seems that this should be sufficient.
In practice everything proved more complicated when each element of the architecture began to conflict with the others, especially when several contractor teams participated and each team held its own vision of how the network and security architecture should look.
At one point the discussions started to resemble an engineering construction set: every party offered its own solution, and the task was to assemble from these proposals a working and scalable system.
Related articles
Building Resilient DoH Failover on MikroTik RouterOS to Handle Unreachable Cloudflare Responses
A network administrator encountered a persistent issue in a branch office where pages like Tailwind CSS CDN failed to load despite valid DNS responses from Cloudflare DoH. The problem stemmed from unreachable IP addresses such as 8.6.112.0 and 8.47.69.0 returned by the resolver, which RouterOS treated as healthy because it only checked for valid IP types rather than route reachability. RouterOS supports only a single active DoH upstream via the use-doh-server parameter, requiring custom scripting for failover between multiple endpoints like Cloudflare and dns.google. The solution involved static DNS entries for bootstrap addresses, certificate trust anchors including SSL.com TLS ECC Root CA 2022, and a health monitor script that probes using DNS-JSON API calls instead of switching the resolver directly. Multiple iterations addressed issues like cache-based false positives, plain DNS fallback risks from provider spoofing, and clock validation to prevent certificate failures. The final implementation uses thresholds for failure and recovery to avoid flapping and ensures post-switch verification before committing to a backup endpoint.
NetRuleRouter Alpha Released to Route Traffic Across Multiple Connections Without Disabling VPN
Developer krox1 has released the first public alpha of NetRuleRouter v0.1.0-alpha.1 for Windows and Linux, a local network policy manager that distributes traffic between primary and secondary connections based on domains, IP ranges, applications, and subnets. The tool emerged from practical issues that intensified after Russian authorities discussed VPN restrictions in March 2026, with operators and platforms later prompting users to disable VPN for domestic services. NetRuleRouter sits on top of existing connections rather than acting as a VPN client or proxy, allowing users to keep corporate VPNs, personal VPNs, and direct internet active simultaneously. It supports seven matching methods including exact domains, wildcard subdomains, CIDR ranges, and application paths, with priority rules to resolve overlaps and built-in leak protection that prevents protected destinations from falling back when the secondary connection drops. The alpha includes diagnostic tracing, preset rule sets for Russia and other regions, import/export capabilities, and a first-run wizard that configures the background service and initial bindings. Limitations around DNS, shared IPs, and brief startup windows are documented, and the project explicitly does not protect against account-level blocks by services such as Anthropic.
Setting Up Nextcloud Talk on TrueNAS with Custom Domain for Private Family Calls
A detailed guide explains how to deploy Nextcloud Talk on a TrueNAS server behind a custom domain to create a self-hosted messaging and calling platform for family use. The author addresses problems with commercial messengers such as VK notifications failing on iOS and Telegram requiring VPN connections. The solution uses HestiaCP on a VPS for reverse proxying, Let's Encrypt SSL certificates, and port forwarding on a home router to reach the TrueNAS instance at 192.168.0.17:30027. Additional steps cover configuring coturn for TURN relay to enable reliable voice and video calls, updating trusted domains in Nextcloud, and disabling router DoS protection. The setup also enables Screen Sharing, reactions, and push notifications while keeping all data under user control.
Aladdin Launches Enterprise CA 3.0 with Kubernetes Support and Fourfold Faster Certificate Issuance
Russian vendor Aladdin has released version 3.0 of its corporate certificate authority product, Aladdin Enterprise CA. The update emphasizes Kubernetes and Deckhouse integration to automate certificate lifecycle management and improve cluster resilience. Mass issuance of file-based certificates is now up to four times faster than in the previous release. The product includes native ACME protocol support for automated SSL certificate deployment and adds centralized security logging with SIEM integration. It is positioned as a drop-in replacement for Microsoft CA that allows migration without service interruption. Additional features include support for RED Database, an English-language interface, and expanded administrative capabilities. The new version is currently undergoing FSTEC Russia certification while version 2.x continues to receive security updates.