From 34f4470a1520ce25eddd9907c7c65792899f059e Mon Sep 17 00:00:00 2001 From: =?utf8?q?Stefan=20B=C3=BChler?= Date: Sat, 11 May 2013 11:00:30 +0200 Subject: [PATCH] Split the SOA-EDIT modes into a list, reorder, add some notes and fix the old ones --- pdns/docs/pdns.xml | 70 ++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 59 insertions(+), 11 deletions(-) diff --git a/pdns/docs/pdns.xml b/pdns/docs/pdns.xml index 9a1b7f13d..b7d54e98a 100644 --- a/pdns/docs/pdns.xml +++ b/pdns/docs/pdns.xml @@ -12636,17 +12636,65 @@ sql> insert into domainmetadata (domain_id, kind, content) values (7,'ALLOW-AXFR When serving this zone, modify the SOA serial number in one of several ways. Mostly useful to get slaves to re-transfer a zone regularly to get fresh RRSIGs. - - Available modes are: INCEPTION (which sets the SOA Serial to - the current two-week signing period start in YYYYMMDD01 format), - INCEPTION-WEEK (number of weeks since the - epoch), INCREMENT-WEEKS (which increments the serial with - the number of weeks since the epoch), EPOCH (number of - seconds since the epoch). Finally, INCEPTION-EPOCH - (available since 3.1) is special and sets the new SOA serial - number to the maximum of the old SOA serial number, and age - in seconds of the start of the current signing period. - + + Inception refers to the time the RRSIGs got updated in live mode. This happens every week (see ). The inception time does not depend on local timezone, but some modes below will use localtime for representation. + + + Available modes are: + + + INCREMENT-WEEKS + + + Increments the serial with the number of weeks since the epoch. + + + This should work in every setup; but the result won't look like YYYYMMDDSS anymore. + + + + + INCEPTION-EPOCH (available since 3.1) + + + Sets the new SOA serial number to the maximum of the old SOA serial number, and age in seconds of the last inception. + + + This requires your backend zone to use age in seconds as SOA serial. The result is still the age in seconds of the last change. + + + + + INCEPTION (not recommended) + + + Sets the SOA serial to the last inception time in YYYYMMDD01 format. Uses localtime to find the day for inception time. + + + The SOA serial will only change on inception day, so changes to the zone will get visible on slaves only on the following inception day. + + + + + INCEPTION-WEEK (not recommended) + + + Sets the SOA serial to the number of weeks since the epoch, which is the last inception time in weeks. + + Same problem as INCEPTION + + + + EPOCH + + + Sets the SOA serial to the number of seconds since the epoch. + + Don't combine this with AXFR - the slaves would keep refreshing all the time. If you need fast updates, sync the backend databases directly with incremental updates (or use the same database server on the slaves) + + + + -- 2.50.0