nsd users - Jan 2013 - Featurerequest for nsd4

Hello Wouter,

We used tinydns for many years. After migration to nsd3 we miss only one feature
present in tinydns only:

tinydns may switch addresses by decreasing the ttl for old data and serve new
data
starting from a fixed timestamp.

http://cr.yp.to/djbdns/tinydns-data.html:
You may include a timestamp on each line. If ttl is nonzero (or omitted),
the timestamp is a starting time for the information in the line; the line will
be ignored before that time.
If ttl is zero, the timestamp is an ending time (``time to die'') for
the information in the line;
tinydns dynamically adjusts ttl so that the line's DNS records are not
cached for more than a few
seconds past the ending time. A timestamp is an external TAI64 timestamp,
printed as 16 lowercase hexadecimal characters. For example, the lines

     +www.heaven.af.mil:1.2.3.4:0:4000000038af1379
     +www.heaven.af.mil:1.2.3.7::4000000038af1379
----

Do you think, it could be possible with nsd too?
Andreas


-- 
Andreas Schulze
Internetdienste | P252

DATEV eG
90329 N?rnberg | Telefon +49 911 319-0 | Telefax +49 911 319-3196
E-Mail info @datev.de | Internet www.datev.de
Sitz: 90429 N?rnberg, Paumgartnerstr. 6-14 | Registergericht N?rnberg, GenReg
Nr.70
Vorstand
Prof. Dieter Kempf (Vorsitzender)
Dipl.-Kfm. Wolfgang Stegmann (stellvertretender Vorsitzender)
Dipl.-Kfm. Michael Leistenschneider
Dipl.-Kfm. Dr. Robert Mayr
J?rg Rabe v. Pappenheim
Dipl.-Vw. Eckhard Schwarzer
Vorsitzender des Aufsichtsrates: Reinhard Verholen

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Andreas,

On 01/28/2013 01:24 PM, Andreas Schulze wrote:
> Hello Wouter,
> 
> We used tinydns for many years. After migration to nsd3 we miss
> only one feature present in tinydns only:
> 
> tinydns may switch addresses by decreasing the ttl for old data and
> serve new data starting from a fixed timestamp.
> 
> http://cr.yp.to/djbdns/tinydns-data.html: You may include a
> timestamp on each line. If ttl is nonzero (or omitted), the
> timestamp is a starting time for the information in the line; the
> line will be ignored before that time. If ttl is zero, the
> timestamp is an ending time (``time to die'') for the information
> in the line; tinydns dynamically adjusts ttl so that the line's DNS
> records are not cached for more than a few seconds past the ending
> time. A timestamp is an external TAI64 timestamp, printed as 16
> lowercase hexadecimal characters. For example, the lines
> 
> +www.heaven.af.mil:1.2.3.4:0:4000000038af1379 
> +www.heaven.af.mil:1.2.3.7::4000000038af1379 ----
> 
> Do you think, it could be possible with nsd too?
This is a fairly substantial feature request, and cannot be in NSD 4.0
(which is now in beta and such large features are no longer accepted).
 For 4.x, I am ambivalent, the question is how many people must have
this option versus its implementation complexity.

TTL=10 seconds instead of this feature, would that not have almost the
same semantics, except for higher server load before the timestamp is
reached?  Is it about server load, and I think not, because the
timestamp creates a high server load peak, where a normal changeover
with a fixed TTL spreads out the query volume.

Best regards,
   Wouter

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRB8sKAAoJEJ9vHC1+BF+NLVAP/iduPsxiyHTWkPnb/9VhhTWf
4zNfBy9QF7uGXmG5Nq1BRRoH2upX6MmyAWGX4fHvawSjyp18xzKy5VrFp7Ag9Bqz
kmFBqyab2nvKUc7eF2C4KwcbhmtccdgdfNHSeu59b4AtwcATQk/iP7GiTKMZmco6
935+R16I3PQzPVTGzREtinQkcBrB14QqKCDMicUtBP7vLOkd3fwXuR5sh3wKDHfc
9u4b62TpLFL5cNhea8glMytpxvMR3rlsn/aTnR4+OMuQtQlP3/eeELhDE6uQiMU2
dRbmYA3pNZMsNJBWr05dkP8/gO1U0d7w+HxwxdWZexbxAuV4d7AcRkDx5x2ydIT1
RuclJq1cPc1ufkowjfWIyfKlySI12DRiuT6owXq/UOJ73dSQbEJuec1UwIrWMXrb
A/0dXU78xhkau4MSAfzqOXI21dYFLag+E5YrAKJAGs9Xqlc2x2WvVKygybxhcdp5
wOUyqP+1Ln6jqAOeSzfTmsyEboZ5t9kmK4zuxNvYqZ0c9xdeShWakGr67lZKik5V
uF1GrwWJiZa5f6Li9BGC4D+Ri4dlZijiIxRnmEEAGI59NkqfIoZXt6J47B+1tx+3
8K2S3I4/BuaAcY9rTNr+ayXk+Bwb25sYnOWzhGmHuzuCa60nxkygmK1miO0hS/+R
g5ooXBjNIV3t4yNNK6qV
=eLSB
-----END PGP SIGNATURE-----