# DNS Published articles for DNS. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## \[Podcast\] 'Just say no' isn't as simple as you think DevFeed: [\[Podcast\] 'Just say no' isn't as simple as you think]() Original publisher: [Read original article]() Author: George Michaelson Published: 2026-09-16T23:23:11Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [APNIC Labs](), [Protocol (disambiguation)](), [Server]() Tags: [apnic-labs](), [dns](), [measurement](), [podcast](), [protocol](), [tech-matters]() ### AI overview A PING podcast episode continues a discussion of surplus DNS queries observed in an APNIC Labs experiment. It examines how different ways of answering negatively affect query volume and the work required by servers, resolvers, and clients, and considers whether maintaining transport protocol state could reduce repeated-query work. ### Source excerpt A continuation of the discussion on surplus DNS queries seen at APNIC Labs, the implications of how you say 'no', and the transport used for the DNS ## Running a Self-Hosted Tailscale Control Server Behind a Reverse Proxy DevFeed: [Running a Self-Hosted Tailscale Control Server Behind a Reverse Proxy]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-15T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [tailscale](), [proxy](), [traefik](), [TLS (Transport Layer Security)](), [TLS handshake](), [Self-hosted](), [Homelab]() Tags: [dns](), [docker](), [h2](), [homelab](), [networking](), [proxy](), [reverse-proxy](), [security](), [self-hosted](), [tailscale](), [tls](), [tls-handshake](), [traefik]() ### AI overview This tutorial explains how to run a self-hosted Tailscale control server, Headscale, behind Traefik. It finds that the reverse proxy must use TLS with HTTP/1.1 only because Tailscale's noise handshake expects a full-duplex byte stream and can fail when ALPN negotiates HTTP/2. ### Source excerpt Headscale behind Traefik: tls.options=no-h2@file with alpnProtocols http/1.1, because the Tailscale noise handshake breaks when ALPN negotiates h2. ## One or two nameservers? DevFeed: [One or two nameservers?]() Original publisher: [Read original article]() Author: Geoff Huston Published: 2026-09-15T06:01:49Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [Internet](), [Query (disambiguation)](), [Server](), [Caching]() Tags: [2026](), [africa](), [article](), [china](), [dns](), [europe](), [experiment](), [india](), [internet](), [ipv4](), [ipv6](), [measurement](), [measurements](), [recursive-resolver](), [repeat](), [responses](), [server](), [tech-matters]() ### AI overview This article reports an experiment testing whether serving a DNS zone with two authoritative dual-stack nameservers changes repeated queries. Compared with one nameserver, two nameservers increased the single-query completion rate from 58% to 71% and reduced the average queries per test from 3.43 to 2.57. ### Source excerpt Do multiple dual-stack nameservers increase or decrease repeat DNS queries? The results of this experiment were a complete surprise. ## I Added Break-Glass Accounts Before My Home Lab Locked Me Out DevFeed: [I Added Break-Glass Accounts Before My Home Lab Locked Me Out]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-09-14T12:16:15Z Content type: article Language: en Sources: [Virtualization Howto]() Topics: [Homelab](), [Authentication](), [Single sign-on (SSO)](), [Docker](), [Database](), [networking](), [Server](), [Amazon Route 53]() Tags: [authentication](), [container](), [database](), [dns](), [docker](), [home-lab](), [home-server](), [infrastructure](), [networking](), [server](), [sso]() ### AI overview The article explains why a home lab that centralizes authentication through single sign-on can become inaccessible during an outage. It introduces "break glass" accounts as a recovery measure and emphasizes treating the authentication service as infrastructure with dependencies such as its application, database, certificates, networking, reverse proxy, and DNS. ### Source excerpt One of the coolest things that you can do is centralize your authentication in the home lab. So, instead of having all kinds of separate usernames and passwords that are... The post I Added Break-Glass Accounts Before My Home Lab Locked Me Out appeared first on Virtualization Howto. ## 1.1.1.1 now supports post-quantum DNSSEC, all 2,420 bytes of it DevFeed: [1.1.1.1 now supports post-quantum DNSSEC, all 2,420 bytes of it]() Original publisher: [Read original article]() Author: Bas Westerbaan Published: 2026-09-10T13:00:00Z Content type: article Language: en Sources: [Cloudflare Blog]() Topics: [Cryptography]() Tags: [1-1-1-1](), [algorithms](), [cryptography](), [dns](), [dnssec](), [post-quantum](), [research](), [security](), [testing](), [tls](), [validation]() ### AI overview Cloudflare's 1.1.1.1 now validates DNSSEC signatures using the post-quantum ML-DSA-44 algorithm. The article discusses testing oversized DNS responses and preventing downgrade to conventional signatures while retaining compatibility with older resolvers. ### Source excerpt 1.1.1.1 now validates DNSSEC signatures using NIST's post-quantum ML-DSA-44 algorithm. Here is how we manage 2,420-byte signatures and downgrade risks at scale. ## Microsoft fixes record 964 flaws, including 2 exploited zero-days DevFeed: [Microsoft fixes record 964 flaws, including 2 exploited zero-days]() Original publisher: [Read original article]() Author: Pieter Arntz Published: 2026-09-09T10:01:08Z Content type: news Language: en Sources: [Malwarebytes]() Topics: [Vulnerabilities]() Tags: [bugs](), [cve-2026-81963](), [cve-2026-85880](), [dns](), [microsoft](), [news](), [patch-tuesday](), [september-2026](), [vulnerabilities](), [windows]() ### AI overview Microsoft's September 2026 Patch Tuesday fixes 964 customer-patched vulnerabilities, including two actively exploited Windows zero-days. ### Source excerpt Microsoft's September 2026 Patch Tuesday fixes a record 964 vulnerabilities, including two actively exploited zero-days. ## Building resilient self hosted services is not always easy DevFeed: [Building resilient self hosted services is not always easy]() Original publisher: [Read original article]() Author: George Michaelson Published: 2026-09-09T05:10:54Z Content type: opinion Language: en Sources: [APNIC Blog]() Topics: [Pi-hole](), [Resilience](), [Network Configuration](), [systems](), [Server]() Tags: [dns](), [infrastructure](), [network](), [resilience](), [router](), [self-hosted](), [server](), [systems](), [tech-matters]() ### AI overview The article reflects on the difficulties of running resilient self-hosted DNS services at home. It describes how reboots and router or DNS configuration changes can disrupt DHCP and the wider home network, arguing for independently configured redundant instances and a tested backup plan. ### Source excerpt Resiliency through more redundancy is important no matter the scenario. ## Troubleshooting Wi-Fi at Black Hat USA 2026 with ThousandEyes DevFeed: [Troubleshooting Wi-Fi at Black Hat USA 2026 with ThousandEyes]() Original publisher: [Read original article]() Author: Alex Guckin Published: 2026-09-07T15:00:39Z Content type: article Language: en Sources: [Security @ Cisco Blogs]() Topics: [Network Operations Center](), [dashboards](), [telemetry](), [Duo]() Tags: [agents](), [black-hat](), [cybersecurity](), [dns](), [duo](), [metrics](), [monitoring](), [network-operations-center](), [noc](), [operations](), [security](), [security-operations-center](), [soc](), [splunk-cloud](), [splunk-enterprise-security](), [thousandeyes]() ### AI overview A behind-the-scenes account of using ThousandEyes monitoring nodes and dashboards to troubleshoot Wi-Fi performance and roaming issues in the Black Hat USA 2026 Network Operations Center. ### Source excerpt A behind-the-scenes look at troubleshooting Wi-Fi in the Black Hat USA 2026 Network Operations Center with ThousandEyes. ## Distributed Latency Monitoring at Black Hat DevFeed: [Distributed Latency Monitoring at Black Hat]() Original publisher: [Read original article]() Author: Adam Kilgore Published: 2026-09-07T15:00:37Z Content type: article Language: en Sources: [Security @ Cisco Blogs]() Topics: [dashboards]() Tags: [black-hat](), [command-line](), [cybersecurity](), [dashboards](), [dns](), [latency](), [linux](), [monitoring](), [network-operations-center](), [noc](), [security](), [thousandeyes]() ### AI overview The article describes a ThousandEyes-based monitoring mesh at Black Hat USA that tracks latency, availability, download speed, and protocol-specific behavior. It combines dashboards and automated tests with on-demand Linux command-line checks for rapid troubleshooting. ### Source excerpt Learn how the Black Hat NOC/SOC used ThousandEyes, Linux command-line testing, and packet evidence to monitor distributed latency, isolate DNS issues, and validate network performance during a live cybersecurity event. ## Building a Risk-Based Secure Network Analytics Detection with Splunk Detection Editor (Alpha) DevFeed: [Building a Risk-Based Secure Network Analytics Detection with Splunk Detection Editor (Alpha)]() Original publisher: [Read original article]() Author: Aditya Sankar Published: 2026-09-07T15:00:32Z Content type: article Language: en Sources: [Security @ Cisco Blogs]() Topics: [Network](), [incident]() Tags: [black-hat](), [building](), [cybersecurity](), [data](), [dns](), [documentation](), [firewall](), [network-operations-center](), [noc](), [security](), [security-operations-center](), [soc](), [splunk-cloud](), [splunk-enterprise-security]() ### AI overview This article explains how to use Splunk Detection Editor (Alpha) to develop a Cisco Secure Network Analytics detection and add its alarms as risk events in Splunk Enterprise Security. It covers SPL development and testing, sample data, risk scoring, CIM fields, and investigation drilldowns, with risk-based alerting used to correlate behavior over time. ### Source excerpt At Black Hat USA, we used Splunk Detection Editor Alpha to turn Cisco SNA alarms into risk events with context, drilldowns & analyst-ready investigation paths. ## Black Hat USA 2026: Safeguarding DNS with Secure Access DevFeed: [Black Hat USA 2026: Safeguarding DNS with Secure Access]() Original publisher: [Read original article]() Author: Steve Vida Published: 2026-09-07T15:00:32Z Content type: article Language: en Sources: [Security @ Cisco Blogs]() Topics: [SIEM, Security, Observability](), [telemetry](), [NOC]() Tags: [apple](), [black-hat](), [cisco-secure-access](), [cisco-security-cloud](), [cisco-talos](), [cisco-xdr](), [cloudflare](), [cybersecurity](), [dns](), [google](), [network-operations-center](), [noc](), [phishing](), [privacy](), [security](), [security-operations-center](), [soc](), [splunk-cloud](), [splunk-enterprise-security](), [statistics](), [telemetry]() ### AI overview Cisco reports on using Secure Access and DNS telemetry to protect the Black Hat USA 2026 network. The article highlights blocking unapproved encrypted DNS resolvers, DNS request statistics, and activity classified as hacking. ### Source excerpt Cisco is the Security Cloud Provider for the Black Hat conferences, over a decade providing DNS Security. Learn about protecting DNS with Secure Access. ## 7 Simple Home Lab HA Projects for This Weekend DevFeed: [7 Simple Home Lab HA Projects for This Weekend]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-09-05T12:22:03Z Content type: tutorial Language: en Sources: [Virtualization Howto]() Topics: [Homelab](), [Availability](), [Pi-hole](), [Docker](), [Containers]() Tags: [availability](), [containers](), [dns](), [docker](), [high-availability](), [home-lab](), [home-server](), [server](), [servers]() ### AI overview This article presents seven simple high-availability projects for a home lab. Its detailed example recommends running two DNS servers, separating them across Docker hosts, configuring primary and secondary DNS addresses, and synchronizing the DNS platforms. ### Source excerpt A lot of times we think about high availability being some complicated or complex thing that we just think in the home lab it isn't worth doing. However, HA doesn't... The post 7 Simple Home Lab HA Projects for This Weekend appeared first on Virtualization Howto. ## I Thought Keepalived Only Protected My Home Lab Servers. Then I Found Track Scripts DevFeed: [I Thought Keepalived Only Protected My Home Lab Servers. Then I Found Track Scripts]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-09-04T12:32:34Z Content type: tutorial Language: en Sources: [Virtualization Howto]() Topics: [Homelab](), [Availability](), [Linux](), [Proxmox](), [Network](), [Protocol (disambiguation)](), [Docker](), [Server](), [configuration]() Tags: [availability](), [dns](), [docker](), [high-availability](), [home-lab](), [home-server](), [linux](), [network](), [proxmox](), [servers](), [virtualization]() ### AI overview The article explains how Keepalived provides high availability for home lab servers by moving a virtual IP address between Proxmox hosts using VRRP. It focuses on track scripts, which allow failover decisions based on application-level checks rather than only complete server failure, with Docker-based DNS services as an example. ### Source excerpt I have used Keepalived in my home lab for quite some time and most of the time, I have thought of it in a very simple way as to what... The post I Thought Keepalived Only Protected My Home Lab Servers. Then I Found Track Scripts appeared first on Virtualization Howto. ## What part of 'No!' is so hard for the DNS understand? DevFeed: [What part of 'No!' is so hard for the DNS understand?]() Original publisher: [Read original article]() Author: Geoff Huston Published: 2026-09-04T01:06:30Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [servers](), [Caching](), [DDoS](), [Cybercrime](), [Availability](), [Bot](), [Script]() Tags: [apnic-labs](), [attacks](), [availability](), [bots](), [caching](), [ddos](), [dns](), [generate](), [measurement](), [random](), [server](), [servers](), [tech-matters]() ### AI overview The article explains how random name attacks overwhelm authoritative DNS servers by generating queries for nonexistent names, bypassing recursive resolver caches and potentially causing domain availability failures. It also describes APNIC Labs' measurement work on nonexistent-domain responses to improve DNS resilience. ### Source excerpt At APNIC Labs we've been experimenting with understanding how the DNS handles requests to resolve nonexistent names to make the DNS more resilient to random name attacks. ## Announcing Appwrite Domains: your registrar and DNS host DevFeed: [Announcing Appwrite Domains: your registrar and DNS host]() Original publisher: [Read original article]() Author: Aditya Oberai Published: 2026-09-04T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [TLS (Transport Layer Security)](), [Cloud]() Tags: [api](), [cloud](), [dns](), [domain](), [organization](), [products](), [tls]() ### AI overview Appwrite announces Appwrite Domains, a feature of Appwrite Cloud that combines domain registration, authoritative DNS hosting, TLS management, and hostname connections for Sites, Functions, and project APIs within an organization. ### Source excerpt Appwrite Domains brings registration, DNS, and TLS into your organization. Buy names across 160+ TLDs, host the zone, and connect Sites and Functions. ## \[Podcast\] Measuring the impact of locally served root zone DevFeed: [\[Podcast\] Measuring the impact of locally served root zone]() Original publisher: [Read original article]() Author: George Michaelson Published: 2026-09-03T01:05:09Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [DNSSEC](), [Network](), [Security](), [Internet Engineering Task Force (IETF)](), [bug]() Tags: [bug](), [dns](), [dnssec](), [ietf](), [measurement](), [network](), [podcast](), [research](), [security](), [standards](), [tech-matters]() ### AI overview This podcast discusses research into locally served root zones, a DNS resolver model that pre-fetches and stores the root zone. The study examined BIND, Unbound, and Knot Resolver across multiple configurations, including in-band retrieval and HTTPS fetching. It identified an Unbound bug and found that root zone updates can generate substantial network traffic, potentially exceeding traffic from more frequent queries for uncached data. ### Source excerpt An analysis of the traffic impacts of locally served root zones, by Ilyas Rahimi at UvA. ## Pi-hole vs AdGuard Home vs Technitium: which DNS ad-blocker to run DevFeed: [Pi-hole vs AdGuard Home vs Technitium: which DNS ad-blocker to run]() Original publisher: [Read original article]() Author: Shed Stack Published: 2026-09-02T18:00:00Z Content type: comparison Language: en Sources: [Shed Stack]() Topics: [Pi-hole](), [Homelab](), [DNSSEC](), [Go Language]() Tags: [ads](), [comparison](), [dns](), [dnssec](), [features](), [go](), [homelab](), [self-hosted]() ### AI overview Practical comparison of Pi-hole, AdGuard Home, and Technitium as self-hosted DNS ad-blockers. Pi-hole emphasizes its mature blocklist ecosystem, AdGuard Home offers a broader built-in feature set and modern interface, and Technitium provides a full DNS server with blocking capabilities for users who want greater control over DNS. ### Source excerpt A practical breakdown of the three self-hosted DNS ad-blockers, from a homelab that actually ran all of them. ## RFC 10001: Operational Guidelines for DNS Transport in Mixed IPv4/IPv6 Environments DevFeed: [RFC 10001: Operational Guidelines for DNS Transport in Mixed IPv4/IPv6 Environments]() Original publisher: [Read original article]() Published: 2026-08-31T00:00:00Z Content type: article Language: fr Sources: [Blog de Stéphane Bortzmeyer]() Topics: [Internet Engineering Task Force (IETF)](), [Internet](), [migration]() Tags: [article](), [dns](), [ietf](), [internet](), [ipv4](), [ipv6](), [migration](), [operational](), [rfc]() ### AI overview This article explains an IETF RFC recommending that DNS servers support queries over both IPv4 and IPv6. It describes the risks of fragmented name resolution in mixed, IPv4-only, and IPv6-only networks and notes that the guidance replaces RFC 3901. ### Source excerpt Vous gérez des serveurs DNS (qu'ils soient des résolveurs (resolveur-dns.html) ou des serveurs faisant autorité (serveur-dns-faisant-autorite.html)) dans un environnement où il y a à la fois IPv4 et IPv6 ? Alors, ce RFC va vous aider. Il remplace le RFC 3901, qui avait été écrit pour un monde très différent, où IPv6 était marginal. Désormais, la recommandation est que tout serveur DNS doit pouvoir servir les requêtes avec les deux versions d'IP. ## I replaced my DNS resolver and the smart home finally shut up DevFeed: [I replaced my DNS resolver and the smart home finally shut up]() Original publisher: [Read original article]() Author: Shed Stack Published: 2026-08-29T15:00:00Z Content type: article Language: en Sources: [Shed Stack]() Topics: [Internet of things](), [Network](), [Pi-hole](), [telemetry]() Tags: [apps](), [devices](), [dns](), [internet](), [local](), [network](), [router](), [smart-home](), [telemetry]() ### AI overview The article describes replacing Pi-hole with AdGuard Home, using device-level DNS rules and VLAN isolation to reduce telemetry from nearly 100 smart-home devices. It also notes maintenance costs, including occasional false blocks, app issues, and manual DNS configuration. ### Source excerpt AdGuard Home and some strict VLANs quieted almost 100 internet connected devices that all wanted to phone home. ## RFC 10037: Registration Data Access Protocol (RDAP) Extension for DNS Time-to-Live (TTL) Values DevFeed: [RFC 10037: Registration Data Access Protocol (RDAP) Extension for DNS Time-to-Live (TTL) Values]() Original publisher: [Read original article]() Published: 2026-08-29T00:00:00Z Content type: article Language: fr Sources: [Blog de Stéphane Bortzmeyer]() Topics: [Protocol (disambiguation)](), [JSON](), [data](), [Perl]() Tags: [article](), [data](), [dns](), [json](), [perl](), [protocol](), [rfc](), [ttl]() ### AI overview This French article explains a new RFC that standardizes an RDAP extension for retrieving DNS TTL values associated with registered domain and name-server objects. It describes the JSON response property, clarifies that the value is the registry-recorded TTL rather than the resolver's remaining cache time, and notes support in several RDAP libraries. ### Source excerpt Puisque le RFC 9803 étend le protocole d'avitaillement EPP pour ajouter des TTL spécifiques aux noms de domaine enregistrés, il était logique que le protocole d'interrogation RDAP permette d'obtenir cette information. C'est ce que permet l'extension normalisée dans ce nouveau RFC. ## Autistici / Inventati et la censure sur leur nom de domaine DevFeed: [Autistici / Inventati et la censure sur leur nom de domaine]() Original publisher: [Read original article]() Published: 2026-08-29T00:00:00Z Content type: article Language: fr Sources: [Blog de Stéphane Bortzmeyer]() Topics: [domain](), [Internet](), [Website]() Tags: [2026](), [article](), [dns](), [domain](), [internet](), [web]() ### AI overview This French article explains the technical effects of the censorship of the autistici.org domain. It discusses DNS publication being disabled at the registry, the resulting NXDOMAIN response, verification through RDAP, and a temporary workaround using the website's IP address. ### Source excerpt Le 28 août 2026, le nom de domaine "autistici.org" a cessé de fonctionner. Que se passe-t-il techniquement ? ## Vercel CLI expands commands for DNS, domains, and projects DevFeed: [Vercel CLI expands commands for DNS, domains, and projects]() Original publisher: [Read original article]() Author: Melkey Moksyakov Published: 2026-08-28T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Command-line interface](), [Terminal](), [API](), [dashboards](), [observability](), [JSON]() Tags: [agents](), [api](), [cli](), [configuration](), [dns](), [json](), [observability](), [projects](), [terminal](), [update](), [vercel](), [web]() ### AI overview Vercel CLI adds commands for managing DNS records, Vercel domains, project state, observability settings, and project members. The commands support structured JSON output and require explicit confirmation for billable or destructive actions. ### Source excerpt The Vercel CLI now provides dedicated commands for managing DNS records, domains, and projects. This brings more of the functionality available through the Vercel dashboard and API to the terminal, where it can be used interactively, in scripts, or by agents. Inspect and update DNS records Retrieve the complete configuration for a DNS record or update it in place using its record ID. vercel dns update supports changes to the record name, type, value, TTL, MX priority, and comment. SRV records can also be updated using their priority, weight, port, and target fields. Renew domains bought on Vercel Renew a domain on demand or control whether it renews automatically. The renewal command displays the current renewal price and asks for confirmation before completing the purchase. Control project state and observability Pause or resume a project and configure its observability features directly from the CLI. Web Analytics and Speed Insights could already be enabled from the CLI; they can now be disabled as well. Add and remove project members Add a project member with a specific role or remove an existing member. All of the new commands support structured JSON output for scripts and agents. Billable or destructive actions require explicit confirmation. Update to version 59.6.2 (or later) of the Vercel CLI to use the new commands: Learn more in the Vercel CLI documentation. Read more ## The lingering legacy of 'reserved' ports DevFeed: [The lingering legacy of 'reserved' ports]() Original publisher: [Read original article]() Author: George Michaelson Published: 2026-08-27T23:29:48Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [Protocol (disambiguation)](), [Network](), [Process](), [Operating system](), [Unix](), [ssh](), [Firewall](), [Internet]() Tags: [dns](), [firewall](), [history](), [internet](), [network](), [ntp](), [opinion](), [process](), [processes](), [ssh](), [systems](), [tech-matters]() ### AI overview An exploration of why reserved TCP and UDP ports persist, tracing conventions such as ports 22, 53, 80, and 443 to early Internet services on multi-user systems. It explains the relationship between ports, protocol-specific daemons, operating-system administration, and modern firewall and service-discovery practices. ### Source excerpt Modern service discovery mechanisms increasingly allow services to run on arbitrary ports, yet DNS may remain the one protocol that cannot fully escape its dependency on the long-established convention of port 53. ## How we saved 100 terabytes of memory by optimizing 1.1.1.1's DNS cache DevFeed: [How we saved 100 terabytes of memory by optimizing 1.1.1.1's DNS cache]() Original publisher: [Read original article]() Author: Sebastiaan Neuteboom Published: 2026-08-27T17:02:35Z Content type: article Language: en Sources: [Cloudflare Blog]() Topics: [Cache](), [Caching](), [Cloudflare](), [Rust](), [benchmarking](), [Latency](), [datacenter]() Tags: [1-1-1-1](), [benchmarking](), [cache](), [cloudflare](), [data-center](), [deep-dive](), [dns](), [engineering](), [latency](), [memory](), [net-maui](), [optimization](), [performance](), [rust]() ### AI overview Cloudflare describes five Rust-level changes to the memory layout of Big Pineapple, the platform behind 1.1.1.1 and other DNS services. The changes reduced DNS cache entry size by over 50%, freed roughly 100 terabytes of memory across the fleet, increased insert throughput by 43%, and reduced lookup latency by 19%. ### Source excerpt Five Rust-level memory optimizations to the DNS cache layout of Big Pineapple cut per-entry memory by 56%, freeing approximately 100 TB of memory across Cloudflare's fleet. [Next page]()