# client Published articles for client. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Build Trust on a Short Software Project DevFeed: [Build Trust on a Short Software Project]() Original publisher: [Read original article]() Author: Viviana Rosas Published: 2026-09-17T12:00:17Z Content type: opinion Language: en Sources: [Atomic Object]() Topics: [trust](), [Software](), [Testing]() Tags: [client](), [progress](), [project](), [project-communication](), [project-team-management](), [regression](), [testing](), [the-software-life](), [trust]() ### AI overview This article explains how software teams can build client trust during short projects. It recommends frequent feedback and check-ins, making progress visible, and using a limited regression test suite focused on important functionality. ### Source excerpt On a short project, clients need evidence not only that work is happening, but that the team knows when to continue, when to change direction, when to raise concern, and how to leave others capable of carrying the work forward. 1. Close the Feedback Loop - Show Responsiveness. It's extremely important to get feedback quickly [...] The post Build Trust on a Short Software Project appeared first on Atomic Spin. ## Logpoints Walkthrough DevFeed: [Logpoints Walkthrough]() Original publisher: [Read original article]() Author: Igor Kulakov Published: 2026-09-16T14:14:04Z Content type: tutorial Language: en Sources: [The JetBrains Blog]() Topics: [IntelliJ IDEA](), [debug](), [debugging](), [gRPC](), [Java](), [2026.2]() Tags: [2026-2](), [bug](), [client](), [command-line](), [debug](), [debugger](), [debugging](), [debugging-tools](), [idea](), [intellij](), [intellij-idea](), [java](), [kotlin](), [logpoints]() ### AI overview This walkthrough explains how to use logpoints in IntelliJ IDEA to investigate a bug in a gRPC client-server example that returns incorrect discount values. It covers reproducing the issue, attaching the debugger to the server, and observing program behavior without suspending execution, including improvements in IntelliJ IDEA 2026.2. ### Source excerpt Modern development tools, especially IntelliJ IDEA, have such comprehensive debugging support that for virtually any niche use case, there is a specialized tool for the job. This can make it hard to know where to begin. If you are new to debugging tools and want the biggest return on your learning investment, the best feature [...] ## MCP went stateless: What changed in the 2026-07-28 spec DevFeed: [MCP went stateless: What changed in the 2026-07-28 spec]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-16T00:00:00Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Model Context Protocol](), [migration](), [HTTP](), [servers](), [client]() Tags: [api](), [client](), [http](), [load-balancer](), [mcp](), [replacement](), [request](), [routing](), [server](), [servers](), [sessions](), [stateless](), [stream]() ### AI overview The 2026-07-28 MCP specification removes protocol-level sessions, the initialize handshake, and stream resumability, making the protocol behave more like an ordinary HTTP API. Most migrations are mechanical, but lost stream requests can cause reliability regressions or duplicated side effects when retried, so side-effecting tools need application-level idempotency keys. The elicitation change also requires architectural rework. ### Source excerpt Sessions, the initialize handshake, and stream resumability are all gone. Here is what replaced them, and what breaks if you ignore it. ## JDBC batching can still issue one round trip per row unless driver statement rewriting is enabled DevFeed: [JDBC batching can still issue one round trip per row unless driver statement rewriting is enabled]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-09-03T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Databases](), [Latency](), [client](), [Code]() Tags: [batching](), [bulk-load](), [client](), [cost](), [database](), [database-performance](), [durability](), [jdbc](), [latency](), [mysql](), [postgresql](), [server](), [sql]() ### AI overview For small database writes, network round trips and transaction overhead can dominate the actual insert work. The article explains that JDBC batching may accept rows into a client-side batch while still sending separate statements unless driver-side statement rewriting is enabled, and that autocommit adds a transaction and durability barrier per row. ### Source excerpt For small writes the per-statement overhead dominates the actual work, so throughput is set by round trips rather than by the database. JDBC batching is the usual fix and it silently does nothing on the wire unless the driver is told to rewrite the statements, so addBatch can look correct while still issuing one round trip per row. Autocommit compounds it by turning every row into its own transaction and its own durability barrier, which is the difference between one fsync and a hundred thousand. ## 【etcd】Lease 与 KeepAlive：TTL、checkpoint 与 Leader 切换 DevFeed: [【etcd】Lease 与 KeepAlive：TTL、checkpoint 与 Leader 切换]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-26T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [etcd](), [Raft](), [Kubernetes](), [Remote Procedure Call (RPC)]() Tags: [api](), [checkpoint](), [client](), [concurrency](), [distributed](), [etcd](), [follower](), [k8s](), [keepalive](), [kubernetes](), [lease](), [lessor](), [primary](), [raft](), [ttl](), [v3](), [v3-5-33](), [watch]() ### 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 的排障落格。 ## Incremental backup on AWS Glacier with rustic DevFeed: [Incremental backup on AWS Glacier with rustic]() Original publisher: [Read original article]() Published: 2026-08-19T21:04:01Z Content type: tutorial Language: en Sources: [Personal blog of Anurag Bhatia]() Topics: [backups](), [restic](), [Amazon Web Services](), [Amazon S3](), [Rust](), [Open Source](), [Feathers]() Tags: [aws](), [aws-glacier-deep-archive](), [backblaze-b2](), [backup](), [backups](), [client](), [config](), [cost](), [data](), [encryption](), [encryption-at-rest](), [incremental](), [lifecycle](), [open-source](), [password](), [restic](), [restore](), [rust](), [rustic](), [s3](), [snapshots]() ### AI overview A practical guide to using rustic, a Rust implementation compatible with restic, for incremental backups with AWS Glacier cold storage. It explains keeping backup data in cold storage while maintaining metadata in S3 Standard or Backblaze B2 so snapshots, incremental backups, and targeted restores remain possible. ### Source excerpt I have been a heavy restic user for several years. In Jan of this year, I tried making restic work with AWS Glacier deep archive but it did not work out. AWS Glacier Deep Archive, for those who may not know, is one of the cheapest storage options, with costs as low as $1/TB, but with very expensive retrieval due to high egress charges from AWS, in addition to retrieval fees, API charges, etc. It can act as a backup of last resort, kind of like insurance if everything else fails, since it costs roughly 1/7th of what Backblaze B2 charges for the same data ($6.95/TB/month). Restic by design is not compatible with Glacier because it stores a mix of data blobs and tree blobs inside /data. Thus, as AWS lifecycle rules move data from S3 Standard to Glacier, basic repo operations start failing. They do have some experimental support as per FAQ, but it did not work out for me when I tried in Jan. A few days back, I came across an open-source project named rustic -- it's a restic implementation in Rust and supports cold storage. The rustic client is compatible with a traditional restic repo. Rustic and cold storage Rustic supports AWS Glacier as well as OVH cold storage. The way it works is: they keep all data in cold storage and a copy of the metadata in hot storage. This additional copy of metadata in hot storage allows operations like incremental backups, viewing snapshots, and requesting restores where only the specific data blobs needed for the restore are pulled from Glacier. This additional hot storage can sit on S3 standard or even Backblaze B2 (which I prefer due to zero API cost). Demo 1) Create repo Let's create two buckets - one in S3 (to store data in Glacier) and one on Backblaze B2 to hold an additional copy of metadata. > rclone mkdir s3:rustic-demo-cold > rclone mkdir b2:rustic-demo-hot 2) Create rustic config profile This file will define the cold and hot repo locations, along with the password file location, restoration command syntax, etc. [repository] repo ## osmo-remsim - osmo-remsim 1.2.0 released DevFeed: [osmo-remsim - osmo-remsim 1.2.0 released]() Original publisher: [Read original article]() Author: lynxis Published: 2026-08-05T16:54:21Z Content type: release Language: en Sources: [Open Source Mobile Communications: News]() Topics: [bug](), [Concurrency](), [log management]() Tags: [bug](), [bug-fixes](), [client](), [crash](), [csv](), [deadlock](), [debug](), [issue](), [logging](), [mutex](), [tracker]() ### AI overview osmo-remsim 1.2.0 is a release containing stability and bug fixes across bankd, remsim-client, remsim-bankd, and related ASN.1 and logging code. The fixes address invalid CSV and TPDU handling, crashes, memory leaks, race conditions, signal handling, slot mapping, byte order, and a logging mutex deadlock. ### Source excerpt 1.2.0 contains stability fixes and bug fixes. [ Alexander Couzens ] * bankd: csv: fix crash on invalid lines * bankd: csv: fail on invalid csv lines * rspro_server: don't access the msg on error cases * rspro_util: asn1 decode: fix memleak when decoding fails * asn1: ber_decoder: disable stack size check on ctx = NULL * asn1: move asn_debug into librspro * Remove unconditional assignment of asn_debug = 0 * rspro_server: use correct byte order in log message "Bankd IP/Port changed to : [ Andreas Eversberg ] * Fix: Remove slot mapping at bankd when client disconnects * Fix: Prevent race conditions when accessing slotmap in bankd * Fix: Prevent bankd from exiting upon SIGPIPE * Fix unhandled (un)mapping events [ Harald Welte ] * remsim-client: Don't attempt to pass on illegal TPDU length * remsim-bankd: Don't pass on illegal TPDUs of illegal length * bankd: Avoid osmocom logging mutex deadlock in signal handling ## The CSS rule that made a hidden field visible DevFeed: [The CSS rule that made a hidden field visible]() Original publisher: [Read original article]() Author: Bastiaan Brink Published: 2026-08-02T00:00:00Z Content type: opinion Language: en Sources: [AS215248 - Notes]() Topics: [CSS](), [Web Development](), [client](), [servers]() Tags: [client](), [css](), [debugging](), [hidden](), [meta](), [server]() ### AI overview The article explains how a CSS rule overrode the HTML hidden attribute, making an operator-only field visible on a peering portal. The field was not a security leak because the server enforced an identity-based allowlist and returned 403 responses for unauthorized requests. ### Source excerpt Every visitor could see an internal field on the peering portal. Not a leak -- the server never trusted it -- but a good reminder about how `hidden` actually works. ## Bridging Pub/Sub to Temporal with Standalone Activities DevFeed: [Bridging Pub/Sub to Temporal with Standalone Activities]() Original publisher: [Read original article]() Author: Houman Kargaran Published: 2026-07-28T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [execution](), [client](), [Latency](), [Cloud]() Tags: [bridging](), [client](), [cloud](), [community](), [execution](), [latency](), [worker](), [workflow]() ### AI overview This guest post explains how Temporal Standalone Activities can connect Pub/Sub message handling to durable execution without wrapping each activity in a Workflow. It describes how this approach can reduce application-side retry, state-tracking, reconciliation, and monitoring complexity, while offering lower latency for short-lived activity executions. ### Source excerpt How a Temporal Standalone Activity bridges Pub/Sub to Durable Execution, keeping your event handler thin. ## ADBC: Arrow's Cross-Platform Database Connectivity API DevFeed: [ADBC: Arrow's Cross-Platform Database Connectivity API]() Original publisher: [Read original article]() Author: Daniel Beach Published: 2026-07-20T13:57:32Z Content type: article Language: en Sources: [Data Engineering Central]() Topics: [API](), [Databases](), [data](), [client]() Tags: [apis](), [arrow](), [client](), [data](), [database](), [rust]() ### AI overview This article explains ADBC, Arrow's database connectivity API. It describes ADBC implementations across several languages and databases, and compares its columnar, minimal-overhead approach with JDBC and ODBC for working with Arrow data. ### Source excerpt Guest Post by Anonymous Rust Dev ## Keycloak Client Libraries 26.0.11 released DevFeed: [Keycloak Client Libraries 26.0.11 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2026-07-15T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [client](), [servers](), [ci](), [migration]() Tags: [2026](), [bugs](), [changes](), [ci](), [client](), [idm](), [kerberos](), [keycloak](), [keycloak-client-libraries-release](), [ldap](), [migration-guide](), [openid-connect](), [release](), [resolved](), [saml](), [sso]() ### AI overview Keycloak Client Libraries 26.0.11 was released on July 15, 2026. The release notes mention an enhancement to sync after the Keycloak server 26.7.0 release and a CI failure issue in keycloak-client. Users are directed to the migration guide before upgrading. ### Source excerpt Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Enhancements #226 Sync after Keycloak server 26.7.0 release client Bugs #222 keycloak-client CI is failing client ## Telegram's Short-Link Domain Was Temporarily Suspended by Montenegro's .me Registry DevFeed: [Telegram's Short-Link Domain Was Temporarily Suspended by Montenegro's .me Registry]() Original publisher: [Read original article]() Published: 2026-07-14T00:00:00Z Content type: article Language: fr Sources: [Blog de Stéphane Bortzmeyer]() Topics: [domain](), [client](), [service]() Tags: [article](), [client](), [dns](), [domain](), [telegram]() ### AI overview Telegram's short-link domain became unavailable after Montenegro's .me registry stopped publishing it in DNS. The article examines the resulting NXDOMAIN responses, resolver caching, and the domain's later reactivation. ### Source excerpt Si vous utilisez le service de messagerie instantanée Telegram, vous avez sans doute vu aujourd'hui 14 juillet 2026, que des services ne marchaient pas, notamment les liens vers des ressources diverses (images, etc). C'est parce que le registre de noms de domaine du Monténégro l'avait décidé. Voyons les détails. ## RFC 9846: The Transport Layer Security (TLS) Protocol Version 1.3 DevFeed: [RFC 9846: The Transport Layer Security (TLS) Protocol Version 1.3]() Original publisher: [Read original article]() Published: 2026-07-12T00:00:00Z Content type: article Language: fr Sources: [Blog de Stéphane Bortzmeyer]() Topics: [TLS (Transport Layer Security)](), [Protocol (disambiguation)](), [Security](), [version](), [Internet Engineering Task Force (IETF)](), [client](), [Internet](), [QUIC]() Tags: [client](), [ietf](), [internet](), [protocol](), [quic](), [rfc](), [security](), [tls](), [version]() ### AI overview This French article explains RFC 9846, which updates the TLS 1.3 standard. It describes TLS as a mechanism for secure client-server communication over untrusted networks, including its relationship with TCP and QUIC, and introduces the protocol's complexity and components. ### Source excerpt Ce RFC met à jour la norme de la version 1.3 du protocole de cryptographie TLS. Il n'y a pas de grand changement par rapport à son prédécesseur, le RFC 8446. ## Keycloak Client Libraries 26.0.10 released DevFeed: [Keycloak Client Libraries 26.0.10 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2026-06-30T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [client](), [Keycloak](), [Documentation]() Tags: [bugs](), [changes](), [client](), [docs](), [guide](), [idm](), [kerberos](), [keycloak](), [keycloak-client-libraries-release](), [ldap](), [openid-connect](), [resolved](), [saml](), [sso]() ### AI overview Keycloak Client Libraries 26.0.10 was released on June 30, 2026. The release includes resolved issues involving supported Keycloak server versions and downstream documentation builds. ### Source excerpt Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Bugs #208 Clarification of supported keycloak server versions client #210 Latest changes break downstream docs build for 26.6 client ## HTTP 206 Partial Content Explained DevFeed: [HTTP 206 Partial Content Explained]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-26T11:37:15Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [HTTP](), [client](), [browser](), [file](), [servers](), [Cache]() Tags: [browser](), [cache](), [cdn](), [client](), [file](), [http](), [http-206](), [http-codes](), [internet-architecture](), [large-files](), [range](), [request](), [server](), [video](), [web-servers](), [web-troubleshooting]() ### AI overview This tutorial explains HTTP 206 Partial Content, a successful response used when a client requests only part of a file or other resource. It describes byte-range requests, the Range and Content-Range headers, and uses such as video playback, resumable downloads, and cache or CDN handling. ### Source excerpt A browser does not always need the whole file at once. Sometimes it only needs a slice of the file. That slice might be the next part of a video or a chunk of a large object sitting behind a CDN. When that happens, the client can request a byte range instead of requesting the ... Read more The post HTTP 206 Partial Content Explained appeared first on Justin Wilson (j2sw). ## pproxy: a forward proxy that load-balances a pool of upstream proxies DevFeed: [pproxy: a forward proxy that load-balances a pool of upstream proxies]() Original publisher: [Read original article]() Published: 2026-06-22T00:00:00Z Content type: article Language: en Sources: [Andika Ahmad Ramadhan -- Blog]() Topics: [proxy](), [client](), [health checks](), [HTTP]() Tags: [client](), [health](), [health-checks](), [http](), [prometheus](), [proxy](), [reload](), [round-robin](), [socks5](), [tls]() ### AI overview This article presents pproxy, a forward proxy that distributes client traffic across upstream proxies. It describes active health checks, round-robin selection, failover within requests, hot configuration reloads, per-user authentication, and Prometheus metrics. ### Source excerpt pproxy is a forward proxy that load-balances client traffic across a pool of upstream proxies with active health checks and hot config reload, so switching proxy providers means editing one config file instead of every client. ## RFC 9987: SSH Agent Protocol DevFeed: [RFC 9987: SSH Agent Protocol]() Original publisher: [Read original article]() Published: 2026-05-28T00:00:00Z Content type: article Language: fr Sources: [Blog de Stéphane Bortzmeyer]() Topics: [OpenSSH](), [ssh](), [Protocol (disambiguation)](), [client](), [Internet Engineering Task Force (IETF)]() Tags: [client](), [ietf](), [openssh](), [protocol](), [rfc](), [ssh]() ### AI overview This French article explains RFC 9987, which standardizes the long-established SSH Agent Protocol. It describes how the agent stores private keys, handles signing requests, and communicates with clients through a client-server protocol using TLV messages. ### Source excerpt Voici encore un RFC qui normalise quelque chose qui existait depuis longtemps : le protocole Agent de SSH. ## Orchestrate temporary rate limit increases on Temporal Cloud namespaces DevFeed: [Orchestrate temporary rate limit increases on Temporal Cloud namespaces]() Original publisher: [Read original article]() Author: Taylor Khan Published: 2026-05-19T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Cloud](), [Provisioning]() Tags: [applications](), [asynchronous](), [automatically](), [capacity](), [client](), [cloud](), [how-to](), [provisioning](), [temporal-concepts](), [ttl](), [workflows]() ### 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. ## Keycloak Client Libraries 26.0.9 released DevFeed: [Keycloak Client Libraries 26.0.9 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2026-04-17T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [client](), [Server]() Tags: [client](), [dependencies](), [idm](), [kerberos](), [keycloak](), [keycloak-client-libraries-release](), [ldap](), [libraries](), [migration-guide](), [openid-connect](), [release](), [resolved](), [saml](), [sso](), [sync](), [update]() ### AI overview Keycloak Client Libraries 26.0.9 was released on April 17, 2026. The release notes mention syncing after the Keycloak server 26.6.0 release and updating dependencies, and direct users to a migration guide for the complete list of changes. ### Source excerpt Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Enhancements #203 Sync after Keycloak server 26.6.0 release client #205 Update dependencies client ## What is the BFF Pattern? DevFeed: [What is the BFF Pattern?]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-04-07T08:41:56Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [BFF](), [Amazon API Gateway](), [backends](), [client](), [interface](), [resiliency](), [Orchestration](), [rate-limiting]() Tags: [api-gateway](), [authentication](), [backends](), [bff](), [cache-control](), [client](), [decoupling](), [mobile](), [rate-limiting](), [resiliency]() ### AI overview The article explains the Backends-for-Frontends (BFF) pattern, in which dedicated API gateways serve different client types such as web browsers, mobile apps, and public or partner APIs. It describes how BFFs tailor APIs, isolate client-specific logic, and support functions including rate limiting, authentication, header sanitization, and cache control. It also discusses benefits such as resiliency, client-specific optimization, and faster development, along with drawbacks including code duplication and increasing complexity. ### Source excerpt And when do you need it? ## How TCP Handshake Works DevFeed: [How TCP Handshake Works]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-03-31T08:17:52Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [Handshake](), [client](), [servers]() Tags: [client](), [communication](), [http-3](), [quic](), [sequence](), [server](), [tcp](), [tcp-handshake]() ### AI overview A tutorial explaining the TCP three-way handshake. It describes how a client sends SYN, a server responds with SYN-ACK, and the client completes the connection with ACK, including the role of initial sequence numbers and control flags. ### Source excerpt The 3 step process ## SSH Key Handling using the macOS keychain and 1Password DevFeed: [SSH Key Handling using the macOS keychain and 1Password]() Original publisher: [Read original article]() Published: 2026-03-18T01:06:07Z Content type: tutorial Language: en Sources: [Signs of Triviality]() Topics: [macOS](), [ssh](), [configuration](), [client]() Tags: [client](), [configuration](), [handling](), [macos](), [ssh](), [using]() ### AI overview A brief tutorial on client-side configuration for handling SSH keys on macOS with the macOS keychain and 1Password. ### Source excerpt Just a few hints on client-side configuration options for handling SSH keys on macOS using the keychain and 1Password. ## Transitioning from REST to gRPC: System Design and Tradeoffs DevFeed: [Transitioning from REST to gRPC: System Design and Tradeoffs]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-03-16T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [gRPC](), [Remote Procedure Call (RPC)](), [Code](), [HTTP](), [JSON]() Tags: [api-design](), [client](), [grpc](), [http](), [json](), [microservices](), [protobuf](), [rest](), [rpc](), [schema](), [server](), [system-design]() ### AI overview This tutorial explains how gRPC uses .proto service definitions and Protocol Buffers to generate typed client and server code, serialize messages, and communicate over HTTP/2. It compares gRPC with REST and recommends gRPC for internal service-to-service calls needing low latency, schema-first contracts, or streaming, while retaining REST with JSON at the edge for browsers and external consumers. ### Source excerpt gRPC defines services in a .proto file, compiles them into typed client and server code, and transports binary protobuf over HTTP/2. Choose it for internal service-to-service calls that need low latency, schema-first contracts, or streaming, and keep REST with JSON at the edge where browsers and external consumers live. ## nsnotifyd-2.4 released DevFeed: [nsnotifyd-2.4 released]() Original publisher: [Read original article]() Published: 2026-02-24T20:08:07Z Content type: release Language: en Sources: [Tony Finch's blog]() Topics: [servers](), [interoperability](), [retry](), [client](), [Web]() Tags: [bug-fixes](), [client](), [dns](), [git](), [interoperability](), [new-feature](), [release](), [retry](), [web]() ### AI overview The nsnotifyd 2.4 release adds an option to direct all SOA queries to a specific server, fixes the nsnotify client's inability to create DNS NOTIFY messages, and improves compatibility with git archive and web front-ends offering tarball downloads. ### Source excerpt The nsnotifyd daemon monitors a set of DNS zones and runs a command when any of them change. It listens for DNS NOTIFY messages so it can respond to changes promptly. It also uses each zone's SOA refresh and retry parameters to poll for updates if nsnotifyd does not receive NOTIFY messages more frequently. It comes with a client program nsnotify for sending notify messages. This nsnotifyd-2.4 release includes a new feature and some bug fixes: The new -S option tells nsnotifyd to send all SOA queries to a specific server. Previously, in response to a NOTIFY message, it would send a SOA query back to the source of the NOTIFY, as specified by RFC 1996. (Typically, a NOTIFY will only be accepted from a known authoritative server for the zone. The target of the NOTIFY responds with a SOA refresh query and zone transfer. But it should avoid trying to refresh from one of the other authoritative servers which might not have received the latest version of the zone.) Mark Felder encountered a situation where it would have been more convenient to fix the address that nsnotifyd sends SOA queries to, because the source of the NOTIFY messages wasn't responding on that address. Since nsnotifyd is intended to work as glue between disparate parts of a system, it makes sense for it to work around awkward interoperability problems. The nsnotify client program was broken and unable to create NOTIFY messages. D'oh! I have adjusted the release process so that it works better with git archive and web front-ends that offer tarball downloads. [Next page]()