diff --git a/content/momentum/4/config-options-summary.md b/content/momentum/4/config-options-summary.md index ccfb99499..2af4a837a 100644 --- a/content/momentum/4/config-options-summary.md +++ b/content/momentum/4/config-options-summary.md @@ -127,6 +127,7 @@ The `Version` column indicated the version(s) of Momentum that support the optio | [disable_chunked](/momentum/mobile/mobile-reference/mobility-mm-7-listener) – Option used with aggregators who do not support chunked transfer-coding (Mobile Momentum) | both | false | 4.0 and later | http_listener, listen, pathway, pathway_group, peer | | [disable_nagle_algorithm](/momentum/4/config/ref-disable-nagle-algorithm) – Disable nagle algorithm on sockets | both | false | 4.0 and later | control_listener, eccluster_listener, ecstream_listener, esmtp_listener, global, http_listener, listen, xmpp_listener | | [disk_queue_drain_rate](/momentum/4/config/ref-disk-queue-drain-rate) – Control the rate at which messages are spooled in on start-up | both | 100 | 4.0 and later | global | +| [dns_cache_negative_ttl](/momentum/4/config/ref-dns-cache-negative-ttl) – How long the DNS response cache keeps a failed lookup | sending | 300 | 5.3.1 and later | global | | [dns_cache_purge_interval](/momentum/4/config/ref-dns-cache-purge-interval) – How often the DNS response cache is scanned for stale entries | sending | 60 | 4.0 and later | global | | [dns_expire_interval](/momentum/4/config/ref-dns-expire-interval) – How often to check for domains with expired DNS information | sending | 10 | 4.0 and later | global | | [dns_failures_to_purge](/momentum/4/config/ref-dns-failures-to-purge) – Configure the maximum number of DNS lookups | sending | 10 | 4.0 and later | domain, global | diff --git a/content/momentum/4/config/index.md b/content/momentum/4/config/index.md index cfc1dca8f..29fd9175e 100644 --- a/content/momentum/4/config/index.md +++ b/content/momentum/4/config/index.md @@ -62,6 +62,7 @@ description: "This chapter provides the definitions of the configuration options | [delivery_response_timeout](/momentum/4/config/ref-delivery-response-timeout) | time to wait for a response to an outbound request | | [disable_nagle_algorithm](/momentum/4/config/ref-disable-nagle-algorithm) | disable nagle algorithm on sockets | | [disk_queue_drain_rate](/momentum/4/config/ref-disk-queue-drain-rate) | control the rate at which messages are spooled in on start-up | +| [dns_cache_negative_ttl](/momentum/4/config/ref-dns-cache-negative-ttl) | how long the DNS response cache keeps a failed lookup | | [dns_cache_purge_interval](/momentum/4/config/ref-dns-cache-purge-interval) | how often the DNS response cache is scanned for stale entries | | [dns_expire_interval](/momentum/4/config/ref-dns-expire-interval) | how often to check for domains with expired DNS information | | [dns_failures_to_purge](/momentum/4/config/ref-dns-failures-to-purge) | configure the maximum number of DNS lookups | diff --git a/content/momentum/4/config/ref-dns-cache-negative-ttl.md b/content/momentum/4/config/ref-dns-cache-negative-ttl.md new file mode 100644 index 000000000..c22923df5 --- /dev/null +++ b/content/momentum/4/config/ref-dns-cache-negative-ttl.md @@ -0,0 +1,40 @@ +--- +lastUpdated: "10/08/2026" +title: "dns_cache_negative_ttl" +description: "dns cache negative ttl how long the DNS response cache keeps a failed lookup dns cache negative ttl 300 How long in seconds the DNS response cache keeps a failed lookup whose answer has no records such as NXDOMAIN a server failure SERVFAIL or a timeout..." +--- + + +## Name + +dns_cache_negative_ttl — how long the DNS response cache keeps a failed +lookup + +## Synopsis + +`dns_cache_negative_ttl = 300` + +## Description + +How long, in seconds, the DNS response cache keeps a failed lookup whose +answer has no records, such as NXDOMAIN, a server failure (SERVFAIL), or a +timeout. Lookups of that name and type get the cached failure until the next +purge after it expires (see +[dns_cache_purge_interval](/momentum/4/config/ref-dns-cache-purge-interval)). + +A failed lookup is kept for `dns_cache_negative_ttl` or +[max_dns_ttl](/momentum/4/config/ref-max-dns-ttl) seconds, whichever is +lower. The value must not be negative. + +The default value is `300` (seconds). RFC 2308 section 7.1 limits a cached +server failure to five minutes; a value above `300` keeps server failures +longer than that. + +## Scope + +`dns_cache_negative_ttl` is valid in the global scope. + +## See Also + +[max_dns_ttl](/momentum/4/config/ref-max-dns-ttl), +[dns_cache_purge_interval](/momentum/4/config/ref-dns-cache-purge-interval) diff --git a/content/momentum/4/config/ref-max-dns-ttl.md b/content/momentum/4/config/ref-max-dns-ttl.md index 4c896af0b..dc15f8ea5 100644 --- a/content/momentum/4/config/ref-max-dns-ttl.md +++ b/content/momentum/4/config/ref-max-dns-ttl.md @@ -1,7 +1,7 @@ --- -lastUpdated: "03/26/2020" +lastUpdated: "10/08/2026" title: "max_dns_ttl" -description: "max dns ttl set the maximum DNS TTL max dns ttl 4294967295 max dns ttl and min dns ttl are optional overrides to the TTL values returned from DNS only as far as resolving SMTP destinations is concerned the DNS cache used by other parts of the system such as..." +description: "max dns ttl set the maximum DNS TTL max dns ttl 4294967295 max dns ttl and min dns ttl are optional overrides to the TTL values returned from DNS Setting a min dns ttl can be used to prevent excessive DNS lookups in the event that an SMTP destination you are delivering mail to has..." --- @@ -16,10 +16,14 @@ max_dns_ttl — set the maximum DNS TTL ## Description -`max_dns_ttl` and `min_dns_ttl` are optional overrides to the TTL values returned from DNS (only as far as resolving SMTP destinations is concerned; the DNS cache used by other parts of the system such as DKIM is not affected by these parameters). Setting a `min_dns_ttl` can be used to prevent excessive DNS lookups in the event that an SMTP destination you are delivering mail to has unreasonably short TTL values for its DNS records. Conversely, `max_dns_ttl` can be used to force lookups to happen more often if a destination domain has excessively long TTL values in its DNS records. Setting this option should only be necessary in exceptional circumstances. +`max_dns_ttl` and `min_dns_ttl` are optional overrides to the TTL values returned from DNS. Setting a `min_dns_ttl` can be used to prevent excessive DNS lookups in the event that an SMTP destination you are delivering mail to has unreasonably short TTL values for its DNS records. Conversely, `max_dns_ttl` can be used to force lookups to happen more often if a destination domain has excessively long TTL values in its DNS records. Setting this option should only be necessary in exceptional circumstances. Default value is `4294967295`. +`max_dns_ttl` also limits how long the DNS response cache keeps a failed +lookup; see +[dns_cache_negative_ttl](/momentum/4/config/ref-dns-cache-negative-ttl). + ## Scope @@ -28,4 +32,5 @@ max_dns_ttl is valid in the global scope. ## See Also -[min_dns_ttl](/momentum/4/config/ref-min-dns-ttl) \ No newline at end of file +[min_dns_ttl](/momentum/4/config/ref-min-dns-ttl), +[dns_cache_negative_ttl](/momentum/4/config/ref-dns-cache-negative-ttl) \ No newline at end of file