GNU bug report logs - #61485
[PATCH] In knot-service, shorten SOA refresh to maximum recommended in RFC 1912.

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: 宋文武 <iyzsong <at> envs.net>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#61485: closed ([PATCH] In knot-service, shorten SOA refresh
 to maximum recommended in RFC 1912.)
Date: Mon, 06 Mar 2023 08:16:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Mon, 06 Mar 2023 16:15:48 +0800
with message-id <87y1oapa6j.fsf <at> envs.net>
and subject line Re: bug#61485: [PATCH] In knot-service, shorten SOA refresh to maximum recommended in RFC 1912.
has caused the debbugs.gnu.org bug report #61485,
regarding [PATCH] In knot-service, shorten SOA refresh to maximum recommended in RFC 1912.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
61485: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61485
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Felix Lechner <felix.lechner <at> lease-up.com>
To: guix-patches <at> gnu.org
Cc: Felix Lechner <felix.lechner <at> lease-up.com>
Subject: [PATCH] In knot-service,
 shorten SOA refresh to maximum recommended in RFC 1912.
Date: Mon, 13 Feb 2023 10:59:43 -0800

The Knot DNS service in Guix uses two days, or 48 hours, for the SOA
refresh interval but that is outside the range of RFC 1912, which is
entitled "Common DNS Operational and Configuration Errors." [1]

Section 2.2 of RFC 1912 recommends a maximum of 12 hours for the SOA
refresh rate: "You can keep it short (20 mins to 2 hours) if you
aren't worried about a small increase in bandwidth used, or longer
(2-12 hours) if your Internet connection is slow or is started on
demand."

This commit sets the default refresh interval at the nearest value
recommended by the standard, which is 12 hours.

Due to the widespread adoption of NOTIFY messages between primary and
secondary DNS servers, the SOA refresh interval has arguably lost some
importance, but the Guix default should still be in line with the
standards.

Values outside the recommended range can provoke warning messages from
services commonly used to find bugs in DNS configurations, such as the
MX Toolbox Super Tool. [2]

[1] https://datatracker.ietf.org/doc/rfc1912/
[2] https://mxtoolbox.com/SuperTool.aspx


---
 gnu/services/dns.scm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gnu/services/dns.scm b/gnu/services/dns.scm
index 50753b7ab6..32fb8c0664 100644
--- a/gnu/services/dns.scm
+++ b/gnu/services/dns.scm
@@ -114,7 +114,7 @@ (define-record-type* <zone-file>
   (serial  zone-file-serial
            (default 1))
   (refresh zone-file-refresh
-           (default (* 2 24 3600)))
+           (default (* 12 3600)))
   (retry   zone-file-retry
            (default (* 15 60)))
   (expiry  zone-file-expiry

base-commit: ee69b60426d4f87ea19e32f757f1e7415ae58879
-- 
2.39.1

[Message part 3 (message/rfc822, inline)]

From: 宋文武 <iyzsong <at> envs.net>
To: Felix Lechner <felix.lechner <at> lease-up.com>
Cc: 61485-done <at> debbugs.gnu.org
Subject: Re: bug#61485: [PATCH] In knot-service, shorten SOA refresh to
 maximum recommended in RFC 1912.
Date: Mon, 06 Mar 2023 16:15:48 +0800

Felix Lechner <felix.lechner <at> lease-up.com> writes:

> The Knot DNS service in Guix uses two days, or 48 hours, for the SOA
> refresh interval but that is outside the range of RFC 1912, which is
> entitled "Common DNS Operational and Configuration Errors." [1]
> [..]

Pushed, thank you!

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.