mod_sasl2_fast: Fix harmless off-by-one error (invalidates existing tokens!) Problem: This was causing the key to become "<token>--cur" instead of the expected "<token>-cur". As the same key was used by the code to both set and get, it still worked. Rationale for change: Although it worked, it's unintended, inconsistent and messy. It increases the chances of future bugs due to the unexpected format. Side-effects of change: Existing '--cur' entries will not be checked after this change, and therefore existing FAST clients will fail to authenticate until they attempt password auth and obtain a new FAST token. Existing '--cur' entries in storage will not be cleaned up by this commit, but this is considered a minor issue, and okay for the relatively few FAST deployments.

Generate a DNS UPDATE order in format suitable for `nsupdate` based on
current port configuration.

Example output:

```
$ prosodyctl mod_dnsupdate -d example.com -t xmpp.example.com example.com
zone example.com
server ns1.example.com
ttl 3600
add _xmpp-client._tcp.example.com IN SRV 1 1 5222
add _xmpp-server._tcp.example.com IN SRV 1 1 5269
```