# TTL

Published articles for TTL.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Local and distributed cache coherence: stale data caused by missed invalidation messages

DevFeed: [Local and distributed cache coherence: stale data caused by missed invalidation messages](<https://devfeed.tech/articles/local-cache-plus-distributed-cache-the-coherence-bill-nobody-budgets-for-39606.md>)

Original publisher: [Read original article](<https://ankit-rana.com/logs/54-local-and-distributed-cache-coherence/>)

Author: hello@ankit-rana.com

Published: 2026-09-17T00:00:00Z

Content type: opinion

Language: en

Sources: [Ankit Rana | Mechanical Sympathy](<https://devfeed.tech/sources/ankit-rana-mechanical-sympathy.md>)

Topics: [Caching](<https://devfeed.tech/topics/caching.md>), [Redis](<https://devfeed.tech/topics/redis.md>), [data](<https://devfeed.tech/topics/data.md>), [Network](<https://devfeed.tech/topics/network.md>)

Tags: [cache](<https://devfeed.tech/tags/cache.md>), [cache-coherence](<https://devfeed.tech/tags/cache-coherence.md>), [caching](<https://devfeed.tech/tags/caching.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [data](<https://devfeed.tech/tags/data.md>), [distributed-cache](<https://devfeed.tech/tags/distributed-cache.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [network](<https://devfeed.tech/tags/network.md>), [redis](<https://devfeed.tech/tags/redis.md>), [ttl](<https://devfeed.tech/tags/ttl.md>)

### AI overview

The article explains that adding an in-process cache in front of a distributed cache can improve latency but creates independently stale copies across service instances. It focuses on Redis pub/sub invalidation, which provides no persistence, acknowledgement, retry, or replay, allowing instances to miss invalidation messages and serve stale data until their TTL expires.

### Source excerpt

An in-process cache in front of a distributed cache removes a network hop and adds one independent copy of the data per instance, each of which can be stale on its own schedule. Invalidation is normally broadcast over pub/sub, which is fire and forget, so any instance that is restarting, garbage collecting or briefly disconnected simply misses the message and serves stale data until its TTL expires. That TTL is not a performance setting, it is the maximum duration of incorrectness.

## Cache invalidation is a distributed systems problem

DevFeed: [Cache invalidation is a distributed systems problem](<https://devfeed.tech/articles/cache-invalidation-is-a-distributed-systems-problem-in-a-convenience-costume-39604.md>)

Original publisher: [Read original article](<https://ankit-rana.com/logs/52-cache-invalidation-distributed-problem/>)

Author: hello@ankit-rana.com

Published: 2026-09-13T00:00:00Z

Content type: tutorial

Language: en

Sources: [Ankit Rana | Mechanical Sympathy](<https://devfeed.tech/sources/ankit-rana-mechanical-sympathy.md>)

Topics: [Cache](<https://devfeed.tech/topics/cache.md>), [Caching](<https://devfeed.tech/topics/caching.md>), [distributed-systems](<https://devfeed.tech/topics/distributed-systems.md>)

Tags: [cache](<https://devfeed.tech/tags/cache.md>), [cache-invalidation](<https://devfeed.tech/tags/cache-invalidation.md>), [caching](<https://devfeed.tech/tags/caching.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [ordering](<https://devfeed.tech/tags/ordering.md>), [race-conditions](<https://devfeed.tech/tags/race-conditions.md>), [redis](<https://devfeed.tech/tags/redis.md>), [ttl](<https://devfeed.tech/tags/ttl.md>)

### AI overview

Cache invalidation coordinates updates between a database and a cache without a shared transaction. The article explains how operation ordering can let a concurrent reader repopulate stale data and recommends writing to the database before invalidating the cache, followed by a second invalidation to close the remaining race.

### Source excerpt

A cache and a database are two stores that must agree, which makes every invalidation a distributed transaction without a coordinator. The ordering matters more than the mechanism: invalidating before the database write leaves a window where a concurrent reader repopulates the cache with the old value and it stays wrong until the TTL expires. Deleting the key rather than writing the new value removes a whole class of ordering bug, because two concurrent deletes commute and two concurrent writes do not.

## Negative caching protects databases from repeated lookups for nonexistent keys

DevFeed: [Negative caching protects databases from repeated lookups for nonexistent keys](<https://devfeed.tech/articles/negative-caching-the-misses-cost-more-than-the-hits-39602.md>)

Original publisher: [Read original article](<https://ankit-rana.com/logs/50-negative-caching-misses-cost-more/>)

Author: hello@ankit-rana.com

Published: 2026-09-09T00:00:00Z

Content type: tutorial

Language: en

Sources: [Ankit Rana | Mechanical Sympathy](<https://devfeed.tech/sources/ankit-rana-mechanical-sympathy.md>)

Topics: [Caching](<https://devfeed.tech/topics/caching.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [Database](<https://devfeed.tech/topics/database.md>), [Security](<https://devfeed.tech/topics/security.md>), [Latency](<https://devfeed.tech/topics/latency.md>)

Tags: [cache](<https://devfeed.tech/tags/cache.md>), [cache-penetration](<https://devfeed.tech/tags/cache-penetration.md>), [caching](<https://devfeed.tech/tags/caching.md>), [database](<https://devfeed.tech/tags/database.md>), [negative-caching](<https://devfeed.tech/tags/negative-caching.md>), [protection](<https://devfeed.tech/tags/protection.md>), [redis](<https://devfeed.tech/tags/redis.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [security](<https://devfeed.tech/tags/security.md>), [ttl](<https://devfeed.tech/tags/ttl.md>)

### AI overview

Negative caching prevents repeated database queries for nonexistent keys by storing a distinguishable marker for negative results. The article explains how partner integrations, scrapers, stale clients, migrations, or attackers can exploit this gap and recommends using a shorter TTL for negative entries.

### Source excerpt

A cache that stores only found values gives you no protection against lookups for things that do not exist, and a miss on a nonexistent key costs the full origin query every single time. If the key is user supplied, an attacker can generate unlimited unique misses and bypass the cache entirely, which is cache penetration. Caching the negative result fixes it, with a shorter TTL than positive entries because a value appearing is a much more likely event than one disappearing.

## Cache stampede: how one expired key takes down the database

DevFeed: [Cache stampede: how one expired key takes down the database](<https://devfeed.tech/articles/cache-stampede-how-one-expired-key-takes-down-the-database-39600.md>)

Original publisher: [Read original article](<https://ankit-rana.com/logs/48-cache-stampede-expired-key/>)

Author: hello@ankit-rana.com

Published: 2026-09-05T00:00:00Z

Content type: tutorial

Language: en

Sources: [Ankit Rana | Mechanical Sympathy](<https://devfeed.tech/sources/ankit-rana-mechanical-sympathy.md>)

Topics: [Cache](<https://devfeed.tech/topics/cache.md>), [Caching](<https://devfeed.tech/topics/caching.md>), [Database](<https://devfeed.tech/topics/database.md>), [consistent hashing](<https://devfeed.tech/topics/consistent-hashing.md>), [Redis](<https://devfeed.tech/topics/redis.md>)

Tags: [cache-stampede](<https://devfeed.tech/tags/cache-stampede.md>), [caching](<https://devfeed.tech/tags/caching.md>), [connection-pool](<https://devfeed.tech/tags/connection-pool.md>), [consistent-hashing](<https://devfeed.tech/tags/consistent-hashing.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [jitter](<https://devfeed.tech/tags/jitter.md>), [query](<https://devfeed.tech/tags/query.md>), [redis](<https://devfeed.tech/tags/redis.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [thundering-herd](<https://devfeed.tech/tags/thundering-herd.md>), [traffic](<https://devfeed.tech/tags/traffic.md>), [ttl](<https://devfeed.tech/tags/ttl.md>)

### AI overview

This article explains how a cache stampede occurs when a hot key expires and many requests simultaneously recompute the same value against the database. It recommends TTL jitter to prevent synchronized expirations and request coalescing so only one caller recomputes while others wait or serve stale data. It also discusses cache warming and consistent hashing for broader cache-failure scenarios.

### Source excerpt

A cache TTL is a scheduled simultaneous failure: every request being served from one key misses at the same instant and goes to the origin together. If the recompute takes two seconds, every request arriving during those two seconds also misses, so the pileup grows faster than it drains. Jitter on the TTL stops keys expiring in lockstep, and request coalescing so only one caller recomputes while the rest wait or serve stale is what stops a single expensive key from saturating the database.

## 【kube-apiserver】选型收束与开放问题：排除树、Kine 与 events 分集群

DevFeed: [【kube-apiserver】选型收束与开放问题：排除树、Kine 与 events 分集群](<https://devfeed.tech/articles/kube-apiserver-kine-events-33972.md>)

Original publisher: [Read original article](<https://quant67.com/post/apiserver/16-selection/16-selection.html>)

Author: Liao Tonglang

Published: 2026-08-28T00:00:00Z

Content type: tutorial

Language: zh

Sources: [土法炼钢 - 系统与基础设施](<https://devfeed.tech/sources/source-4.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Caching](<https://devfeed.tech/topics/caching.md>), [etcd](<https://devfeed.tech/topics/etcd.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [MySQL](<https://devfeed.tech/topics/mysql.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [Raft](<https://devfeed.tech/topics/raft.md>)

Tags: [apiserver](<https://devfeed.tech/tags/apiserver.md>), [churn](<https://devfeed.tech/tags/churn.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [errcompacted](<https://devfeed.tech/tags/errcompacted.md>), [etcd](<https://devfeed.tech/tags/etcd.md>), [events](<https://devfeed.tech/tags/events.md>), [exclusion-tree](<https://devfeed.tech/tags/exclusion-tree.md>), [kine](<https://devfeed.tech/tags/kine.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [open-questions](<https://devfeed.tech/tags/open-questions.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [quota](<https://devfeed.tech/tags/quota.md>), [raft](<https://devfeed.tech/tags/raft.md>), [selection](<https://devfeed.tech/tags/selection.md>), [sql](<https://devfeed.tech/tags/sql.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [storage](<https://devfeed.tech/tags/storage.md>), [ttl](<https://devfeed.tech/tags/ttl.md>), [v1-30-3](<https://devfeed.tech/tags/v1-30-3.md>), [watch-cache](<https://devfeed.tech/tags/watch-cache.md>)

### AI overview

This concluding article presents a mechanism-based decision tree for diagnosing Kubernetes control-plane issues across kube-apiserver and etcd layers. It explains Kine's differing Watch semantics when using SQLite, PostgreSQL, or MySQL backends, discusses routing Kubernetes Events to a separate etcd cluster, and identifies open questions around watch-cache SLOs, compaction, linear reads, and Lease fencing.

### Source excerpt

用机制排除树收束何时查 apiserver 轴、何时穿透 etcd 轴、何时两轴联查；回收 etcd/13 写下的 apiserver 停损线；Kine SQL backend 的 Watch 语义差与 Jepsen 覆盖空白；events --etcd-servers-overrides 分集群运维；列出 watch cache SLO 联合模型、线性读期望与 Lease+fencing 全链路三个开放问题；以 ADR 语言关闭系列边界。

## 【etcd】Lease 与 KeepAlive：TTL、checkpoint 与 Leader 切换

DevFeed: [【etcd】Lease 与 KeepAlive：TTL、checkpoint 与 Leader 切换](<https://devfeed.tech/articles/etcd-lease-keepalive-ttl-checkpoint-leader-33992.md>)

Original publisher: [Read original article](<https://quant67.com/post/etcd/10-lease/10-lease.html>)

Author: Liao Tonglang

Published: 2026-08-26T00:00:00Z

Content type: tutorial

Language: zh

Sources: [土法炼钢 - 系统与基础设施](<https://devfeed.tech/sources/source-4.md>)

Topics: [etcd](<https://devfeed.tech/topics/etcd.md>), [Raft](<https://devfeed.tech/topics/raft.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Remote Procedure Call (RPC)](<https://devfeed.tech/topics/rpc.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [checkpoint](<https://devfeed.tech/tags/checkpoint.md>), [client](<https://devfeed.tech/tags/client.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [etcd](<https://devfeed.tech/tags/etcd.md>), [follower](<https://devfeed.tech/tags/follower.md>), [k8s](<https://devfeed.tech/tags/k8s.md>), [keepalive](<https://devfeed.tech/tags/keepalive.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [lease](<https://devfeed.tech/tags/lease.md>), [lessor](<https://devfeed.tech/tags/lessor.md>), [primary](<https://devfeed.tech/tags/primary.md>), [raft](<https://devfeed.tech/tags/raft.md>), [ttl](<https://devfeed.tech/tags/ttl.md>), [v3](<https://devfeed.tech/tags/v3.md>), [v3-5-33](<https://devfeed.tech/tags/v3-5-33.md>), [watch](<https://devfeed.tech/tags/watch.md>)

### AI overview

This article explains etcd v3.5.33 lease behavior, focusing on the lessor's primary, demote, and promote roles, the KeepAlive renewal path that normally bypasses Raft, lease checkpointing, and TTL changes during leader transitions. It also discusses implications for Kubernetes Node Leases and distributed locks.

### Source excerpt

钉 etcd v3.5.33 lessor 的 primary/demote/promote、KeepAlive 不经 Raft 的 Renew 路径、LeaseCheckpoint 与 Promote 时 TTL 展期，以及 Leader 切换对 Node Lease 的排障落格。

## 【etcd】读路径与一致性：ReadIndex、Serializable 与 Lease read

DevFeed: [【etcd】读路径与一致性：ReadIndex、Serializable 与 Lease read](<https://devfeed.tech/articles/etcd-readindex-serializable-lease-read-33990.md>)

Original publisher: [Read original article](<https://quant67.com/post/etcd/08-read-consistency/08-read-consistency.html>)

Author: Liao Tonglang

Published: 2026-08-26T00:00:00Z

Content type: tutorial

Language: zh

Sources: [土法炼钢 - 系统与基础设施](<https://devfeed.tech/sources/source-4.md>)

Topics: [etcd](<https://devfeed.tech/topics/etcd.md>), [Raft](<https://devfeed.tech/topics/raft.md>), [consensus algorithm](<https://devfeed.tech/topics/consensus-algorithm.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>)

Tags: [consistency](<https://devfeed.tech/tags/consistency.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [etcd](<https://devfeed.tech/tags/etcd.md>), [follower](<https://devfeed.tech/tags/follower.md>), [k8s](<https://devfeed.tech/tags/k8s.md>), [keepalive](<https://devfeed.tech/tags/keepalive.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [lease](<https://devfeed.tech/tags/lease.md>), [linearizable](<https://devfeed.tech/tags/linearizable.md>), [raft](<https://devfeed.tech/tags/raft.md>), [readindex](<https://devfeed.tech/tags/readindex.md>), [resourceversion](<https://devfeed.tech/tags/resourceversion.md>), [revision](<https://devfeed.tech/tags/revision.md>), [serializable](<https://devfeed.tech/tags/serializable.md>), [ttl](<https://devfeed.tech/tags/ttl.md>), [v3-5](<https://devfeed.tech/tags/v3-5.md>), [v3-5-33](<https://devfeed.tech/tags/v3-5-33.md>)

### AI overview

This tutorial explains read consistency in etcd v3.5.33. It distinguishes default linearizable reads using ReadIndex, local Serializable reads that may be stale on followers, and Lease RPC reads handled by the leader outside the Raft log. It also discusses leader changes, apply-index waiting, follower forwarding, MVCC history reads, and implications for Kubernetes apiserver clients.

### Source excerpt

分列 etcd v3.5.33 三种读语义：默认线性一致读的 ReadIndex 循环、Serializable 本地读、Raft ReadOnlyLeaseBased 与不经 Raft 的 Lease 路径；follower 读风险与 K8s 期望。

## 【etcd】排障五轴：Raft/WAL/MVCC/Watch/Lease 口令表

DevFeed: [【etcd】排障五轴：Raft/WAL/MVCC/Watch/Lease 口令表](<https://devfeed.tech/articles/etcd-raft-wal-mvcc-watch-lease-33997.md>)

Original publisher: [Read original article](<https://quant67.com/post/etcd/15-troubleshoot/15-troubleshoot.html>)

Author: Liao Tonglang

Published: 2026-08-26T00:00:00Z

Content type: tutorial

Language: zh

Sources: [土法炼钢 - 系统与基础设施](<https://devfeed.tech/sources/source-4.md>)

Topics: [etcd](<https://devfeed.tech/topics/etcd.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>)

Tags: [apiserver](<https://devfeed.tech/tags/apiserver.md>), [applied-index](<https://devfeed.tech/tags/applied-index.md>), [apply](<https://devfeed.tech/tags/apply.md>), [committed-index](<https://devfeed.tech/tags/committed-index.md>), [compaction](<https://devfeed.tech/tags/compaction.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [errcompacted](<https://devfeed.tech/tags/errcompacted.md>), [etcd](<https://devfeed.tech/tags/etcd.md>), [five-axes](<https://devfeed.tech/tags/five-axes.md>), [incident](<https://devfeed.tech/tags/incident.md>), [keepalive](<https://devfeed.tech/tags/keepalive.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [lag](<https://devfeed.tech/tags/lag.md>), [lease](<https://devfeed.tech/tags/lease.md>), [mvcc](<https://devfeed.tech/tags/mvcc.md>), [node-lease](<https://devfeed.tech/tags/node-lease.md>), [raft](<https://devfeed.tech/tags/raft.md>), [restore](<https://devfeed.tech/tags/restore.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>), [ttl](<https://devfeed.tech/tags/ttl.md>), [v3](<https://devfeed.tech/tags/v3.md>), [v3-5](<https://devfeed.tech/tags/v3-5.md>), [v3-5-33](<https://devfeed.tech/tags/v3-5-33.md>), [wal](<https://devfeed.tech/tags/wal.md>), [watch](<https://devfeed.tech/tags/watch.md>)

### AI overview

This troubleshooting article organizes etcd failures into five diagnostic axes: Raft consensus, WAL persistence and recovery, MVCC storage and capacity, Watch client synchronization, and Lease TTL semantics. It maps symptoms to axes, explains relevant etcdctl health and status fields, and notes Kubernetes control-plane relationships, including apiserver and Node Lease behavior. The article is anchored to etcd v3.5.33.

### Source excerpt

按 Raft、WAL、MVCC、Watch、Lease 五轴做症状否证；解释 etcdctl endpoint status/health 字段语义；并对照 K8s 控制面 apiserver 超时与 Node Lease 漂移。

## Orchestrate temporary rate limit increases on Temporal Cloud namespaces

DevFeed: [Orchestrate temporary rate limit increases on Temporal Cloud namespaces](<https://devfeed.tech/articles/orchestrate-temporary-rate-limit-increases-on-temporal-cloud-namespaces-36053.md>)

Original publisher: [Read original article](<https://temporal.io/blog/temporary-rate-limit-increases>)

Author: Taylor Khan

Published: 2026-05-19T00:00:00Z

Content type: tutorial

Language: en

Sources: [Temporal Blog](<https://devfeed.tech/sources/temporal-blog.md>)

Topics: [Cloud](<https://devfeed.tech/topics/cloud.md>), [Provisioning](<https://devfeed.tech/topics/provisioning.md>)

Tags: [applications](<https://devfeed.tech/tags/applications.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [client](<https://devfeed.tech/tags/client.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [provisioning](<https://devfeed.tech/tags/provisioning.md>), [temporal-concepts](<https://devfeed.tech/tags/temporal-concepts.md>), [ttl](<https://devfeed.tech/tags/ttl.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

This tutorial presents a Temporal Workflow pattern for temporarily increasing rate limits on Temporal Cloud namespaces during predictable or temporary throughput spikes. A parent Workflow raises the capacity limit, starts an asynchronous Child Workflow, and completes to unblock the client; the Child Workflow waits for a designated duration before restoring the original limit.

### Source excerpt

Stop overpaying for peak capacity. Use Temporal Workflows to grant time-bound rate limit increases that revert automatically after the TTL expires.

## Top Cache Eviction Strategies

DevFeed: [Top Cache Eviction Strategies](<https://devfeed.tech/articles/top-cache-eviction-strategies-34689.md>)

Original publisher: [Read original article](<https://newsletter.systemdesigncodex.com/p/top-cache-eviction-strategies>)

Author: Saurabh Dashora

Published: 2026-04-28T09:03:41Z

Content type: tutorial

Language: en

Sources: [System Design Codex](<https://devfeed.tech/sources/system-design-codex.md>)

Topics: [Caching](<https://devfeed.tech/topics/caching.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [App](<https://devfeed.tech/topics/app.md>), [Databases](<https://devfeed.tech/topics/databases.md>), [Redis](<https://devfeed.tech/topics/redis.md>)

Tags: [browsers](<https://devfeed.tech/tags/browsers.md>), [cache](<https://devfeed.tech/tags/cache.md>), [caching](<https://devfeed.tech/tags/caching.md>), [database](<https://devfeed.tech/tags/database.md>), [operating-systems](<https://devfeed.tech/tags/operating-systems.md>), [performance](<https://devfeed.tech/tags/performance.md>), [redis](<https://devfeed.tech/tags/redis.md>), [strategies](<https://devfeed.tech/tags/strategies.md>), [ttl](<https://devfeed.tech/tags/ttl.md>)

### AI overview

The article explains cache eviction as a way to manage limited cache memory and reviews TTL, LRU, and LFU strategies, including their operation, use cases, advantages, and drawbacks.

### Source excerpt

Caching is a crucial technique for improving application performance and responsiveness.

## Montar un servidor DNS autoritativo con BIND9

DevFeed: [Montar un servidor DNS autoritativo con BIND9](<https://devfeed.tech/articles/montar-un-servidor-dns-autoritativo-con-bind9-34054.md>)

Original publisher: [Read original article](<https://tengoping.com/blog/dns-bind9-servidor-autoritativo/>)

Author: Alois

Published: 2026-01-15T00:00:00Z

Content type: tutorial

Language: es

Sources: [tengoping.com](<https://devfeed.tech/sources/tengoping-com.md>)

Topics: [Linux](<https://devfeed.tech/topics/linux.md>), [Debian](<https://devfeed.tech/topics/debian.md>), [rhel](<https://devfeed.tech/topics/rhel.md>), [Ubuntu](<https://devfeed.tech/topics/ubuntu.md>)

Tags: [apparmor](<https://devfeed.tech/tags/apparmor.md>), [debian](<https://devfeed.tech/tags/debian.md>), [dns](<https://devfeed.tech/tags/dns.md>), [linux](<https://devfeed.tech/tags/linux.md>), [resolver](<https://devfeed.tech/tags/resolver.md>), [retry](<https://devfeed.tech/tags/retry.md>), [rhel](<https://devfeed.tech/tags/rhel.md>), [soa](<https://devfeed.tech/tags/soa.md>), [ttl](<https://devfeed.tech/tags/ttl.md>), [ubuntu](<https://devfeed.tech/tags/ubuntu.md>)

### AI overview

A tutorial on setting up an authoritative BIND9 DNS server on Linux, covering forward and reverse zones, SOA values, common record types, distribution-specific paths, and distinctions from Pi-hole.

### Source excerpt

BIND9 autoritativo en Linux: zonas directas e inversas, servidor secundario con TSIG, rndc y buenas prácticas de seguridad.