Internal DNS as Control Plane: Why Resolvers Matter More Than They Seem
Cloudflare announced the general availability of Cloudflare Internal DNS on 20 July 2026 for corporate clients of Cloudflare Gateway. The vendor placed public and internal DNS next to a protective resolver and described the system through three objects: internal zones, views, and resolver policies. This is not a new DNS standard, yet the architectural framework proves useful because it forces separate descriptions of data, audiences, and response-selection rules.
Most hybrid infrastructures run five simultaneous DNS layers. Public authoritative DNS serves the internet, internal DNS lives in directory services, cloud DNS holds private zones in multiple consoles, protective DNS applies gateway policies, and platform DNS handles container discovery. Each layer has its own management tools, TTL habits, change logs, and owners. When one layer is updated and another is forgotten, symptoms appear as balancer problems, VPN faults, or application slowdowns.
The article distinguishes the data plane from the management plane. The data plane carries the query itself through recursion, caching, and authoritative answers. The management plane answers which zones exist, which records are authoritative, which audience sees which view, which queries are blocked or logged, and how changes propagate with audit trails.
Three objects connect context to authoritative data. An internal zone stores records that must never be visible to public authoritative servers. A view groups internal zones so that resolver policy can return different answers for the same name to different audiences such as office staff, contractors, build pipelines, or test environments. Resolver policy routes the query to the correct view, an upstream server, or public recursion and can also block or log requests.
Client devices reach the corporate resolver through DHCP in offices, VPN tunnels for remote workers, local forwarders in branches, or explicit configuration on servers. Container clusters often run their own resolvers and must forward corporate zones outward. Any device that bypasses the corporate resolver breaks the management plane, leaving only documentation instead of control.
Changes must travel through a single, auditable path. Cloudflare routes console, Terraform, and API calls through one DNS Records API that validates, stores, replicates, and invalidates cache entries. The recommended pattern is infrastructure-as-code or API client to validation to durable store to replication to cache management to audit log. Manual edits on individual servers or separate consoles for network and cloud teams create independent states that later produce resolution conflicts.
Public authoritative zones remain outside internal views. Private zones must never be delegated to public name servers, and zone transfers must be restricted by strict access lists. When a record is absent, the resolver policy decides whether to return a negative answer or fall back to public recursion; sensitive internal zones should return negative answers explicitly.
In zero-trust models, DNS can limit network reconnaissance, surface anomalies earlier, and link name requests to user or device context when the platform supplies that context. Groups such as external contractors can receive views without production zones, while devices lacking disk encryption receive only update and management names. DNS logs become an inventory of user and system behavior that complements, but does not replace, application authorization and network controls.
Related articles
Hacker or Engineer? Reconstructing Attack Chains in Industrial OT Networks
Positive Technologies expert Anton Kutepov presents a detailed educational scenario from the Standoff online polygon to demonstrate how security teams can trace an attack from initial perimeter compromise to unauthorized writes on a PLC. The case begins with an unexpected SCADA server command to a hydrocracking unit controller outside the maintenance window. By correlating network traffic, endpoint telemetry, authentication logs, and asset context, analysts reconstruct the full path: exploitation of a vulnerable DMZ system, lateral movement via Kerberoasting and Active Directory certificate abuse, RDP access to an engineering workstation, and finally weakening of Windows Defender on the SCADA server before issuing the control command. The analysis shows that a single permitted industrial protocol operation becomes suspicious only when placed in the context of prior defensive control changes and anomalous access routes. The article stresses that protecting OT environments requires continuous asset inventory, unified telemetry from traffic and endpoints, and pre-approved response playbooks that avoid disrupting the physical process.
Russia Sets 2030 Deadline to Deliver LTE Internet to Small Settlements
The Russian Ministry of Digital Development has outlined a timeline to provide mobile LTE internet access to small settlements with populations between 100 and 1,000 people by the end of 2030. Minister Maksut Shadaev stated in the State Duma that the next major milestone involves connecting an additional 1,800 settlements by 2027. Over the past six years, LTE service has already reached more than 8,000 such localities through the ongoing federal program. The initiative focuses on building the necessary mobile infrastructure rather than guaranteeing signal coverage at every geographic point. Residents in these areas are expected to gain reliable access to standard digital services without needing to search for optimal signal locations. Progress will be measured by actual deployed infrastructure and operational connectivity at the 2027 checkpoint.
Russian Woman Fined 15,000 Rubles for ChatGPT-Generated Bear Image That Sparked Police Hunt
A resident of Magdagachi in Russia's Amur region used ChatGPT to add a bear to a photo of Krasnoarmeyskaya street as a prank on her friend. The realistic image spread through messengers, prompting residents to alert police and sending hunters with equipment to search for the nonexistent animal. The incident reached the district head, causing widespread fear, with one local resident too afraid to leave home or visit the store. The woman later confessed to police that the image was AI-generated, admitted guilt in court under part 9 of article 13.15 of the Russian Code of Administrative Offenses, and received a reduced fine of 15,000 rubles due to her remorse and first offense. Her iPhone 15 was not confiscated after she explained its necessity for work. This marks the second similar case involving AI-generated bears, following a 30,000-ruble fine and iPhone 11 confiscation in Duldurga, Zabaykalye region, in September.
Molniya Messenger Debuts in RuStore as Paid Alternative with End-to-End Encryption
Russian company Red Soft and Chinese partner Passion Tech have released the Molniya messenger on the RuStore platform. The Android application requires a one-time payment of 750 rubles with no additional in-app purchases. Key features include personal and group chats, audio and video calls, channels, a social feed, and short videos, all protected by default end-to-end encryption. Users can send files up to 4 GB, organize up to 30 chat folders, pin 15 conversations or channels, and subscribe to as many as 1,000 channels. The developers aim to reach 15 million users within 18 months after launch. The project was originally scheduled for early 2026 but became available earlier than planned.