k-v.io: on DELETE, don't return the deleted value
We don't return the deleted value because doing that would have the unintended consequence of postponing the deletion: downstream caching servers would cache the deleted value for up to three more minutes. We'd rather have the key deleted sooner rather than later.
Some APIs, e.g. etcd's, return a list of deleted values on return: those APIs can afford to do so because they don't need to worry about DNS propagation.
We also lengthen the timeout of an etcd
API call from 500 msec to 1928 msecs; 500 msec was too close; some calls routinely took 480 msec to complete, and we wanted more headroom.
We also no longer do two etcd
operations when we delete a value. Previously we would do a GET followed by a DELETE, but since we're not returning the value deleted, there's no point to the GET. Furthermore, the GET was never necessary, for the etcd
DELETE API call returned the values deleted.
- We no longer produce BOSH releases; if you need a BOSH release, use version 2.5.1.
- You can now select the port to bind to, e.g.
sslip.io-dns-server -port 5353
. This is useful, for example, when you're not running as a privileged user, and you can't bind to a privileged port (e.g. 53). - Blocklists are downloaded once per hour, not once per hour per IP address bound to.