At 17:14, we accidentally published a DNSSEC key for tuxis.net. This was caused by an error in a manually executed script. At 17:25, we updated the tuxis.net-zone to retract the DNSSEC key.
For our own network, we have flushed the incorrect records from our resolvers, after which tuxis.net was resolvable again. In all other situations, if you have resolved a hostname within tuxis.net and your resolver has DNSSEC-validation enabled, you may have received a SERVFAIL as a response, instead of the correct response. The DNSSEC record has a TTL of 1 day, which we cannot change or retract. If you are still having issues with resolving tuxis.net hostname (this includes hostnames that CNAME to a tuxis.net record, such as pbs001.tuxis.nl) you can flush all the existing tuxis.net records from your resolver, or restart your resolving nameservers.
You may also have issues with MX-records that point to saas.tuxis.net machines with Kerio in the Cloud services.
We apologise for the inconvenience.
