Domain held hostage, DNSSEC to the rescue

Update 2015-09-29 22:00: At this time, the whois information has been corrected.
For the upcoming 24 hours, intermittent failures are expected due to DNS propagation.

As some of you might have noticed, my domain name, which I use for my personal email, has been offline as of last sunday (2015-09-27).
The reason is an "administrative issue" (read: unpaid bill) between the company I registered my domain with and the registrar they use, Network Solutions, and it seems that they took the customers' domain names as "ransom".
(Note: I have paid my bill, it was xs4all that didn't pay their bill to Network Solutions as far as I've heard).
The domains were marked as PENDING-DELETING, and have been provided with rogue nameserver records.
Those nameservers are even serving MX records for mail servers controlled by Network Solutions, making sure that every email sent to my domain gets sent to mail servers controlled by Network Solutions, an American company I have no contract with whatsoever.
What happened to my email is anyone's guess, all I know is that I don't have them.

Luckily, I have deployed DNSSEC on this domain, and when taking over the records on the domain, they left my DNSSEC public keys in the registry.
This means that resolvers that verify DNSSEC will refuse to resolve my domain, since they (obviously) do not have my DNSSEC keys.
I would like to sincerely thank Paul Wouters with his help explaining me all about DNSSEC before!

Luckily I had another domain name ( that I could also use, and I can also receive emails on that.

I will post an update to this blog post as soon as this issue has been fixed.

Fedora OpenID issues resolved

Fedora Infrastructure over to Ipsilon