Activity
From 2023-03-14 to 2023-04-12
2023-04-12
-
21:54 Feature #59: DNSSEC should be implemented for BitFolk domains
- The remaining zones have now been DNSSEC-signed.
SSHFP records have been added for things customers are expected t...
2023-04-11
-
14:19 Feature #59: DNSSEC should be implemented for BitFolk domains
- The remainder of the IPv4 reverse zones have now been DNSSEC-enabled.
I've just realised that there will have to b... -
13:33 Feature #59: DNSSEC should be implemented for BitFolk domains
- Now DNSSEC-enabled:
* @bitfolk.co.uk@
* @87.119.85.in-addr.arpa@
2023-04-10
-
02:56 Feature #59: DNSSEC should be implemented for BitFolk domains
- Fix typo in task description
-
02:50 Feature #59: DNSSEC should be implemented for BitFolk domains
- I forgot about @autov6rev.bitfolk.space@ which is used for dynamically-generated host names for customers who do not ...
-
02:41 Feature #59: DNSSEC should be implemented for BitFolk domains
- DNSSEC has already been implemented for the following domains:
* @0.0.0.0.7.0.1.1.a.0.a.2.ip6.arpa@
* @136.168.18... -
02:37 Feature #59: DNSSEC should be implemented for BitFolk domains
- Fix typo in task description
-
02:35 Feature #59: DNSSEC should be implemented for BitFolk domains
- The following domains are managed by Jump who do not want to delegate DNSSEC.
They would rather we moved away from u...
Also available in: Atom