Skip to main content

unicolet.org continued

I contacted AIT which is, well was, the registrar of unicolet.org until last november. They say they tried to contact me about the renewal of the domain but I failed to answer so the registration expired. In fact I never received any email from AIT regarding the domain renewal not only this year but also in the past 4 years years that I've been with them.
Also they don't know or can't say what the emails were about because they are generated from an automated system. They only aknowledge the email was sent to my gmail account on certain dates before the renewal expiry date. Now this looks strange to me: it has indeed happened that gmail marked legitimate emails as spam, but it happened very rarely. Because of this gray area I can't make up whether the failure to renew unicolet.org was on my or AIT's side (so I guess I'll just blame myself for not checking more thoroughly).

Lessons learned: if you have registered any domain make sure that your registrar is actually renewing the registration. It could be a very bitter morning when you wake up to find out that it was taken from somebody else.

This is a link to another case of cyber squatting.
Labels:

Comments

Post a Comment

Popular posts from this blog

Mirth: recover space when mirthdb grows out of control

I was recently asked to recover a mirth instance whose embedded database had grown to fill all available space so this is just a note-to-self kind of post. Btw: the recovery, depending on db size and disk speed, is going to take long. The problem A 1.8 Mirth Connect instance was started, then forgotten (well neglected, actually). The user also forgot to setup pruning so the messages filled the embedded Derby database until it grew to fill all the available space on the disk. The SO is linux. The solution First of all: free some disk space so that the database can be started in embedded mode from the cli. You can also copy the whole mirth install to another server if you cannot free space. Depending on db size you will need a corresponding amount of space: in my case a 5GB db required around 2GB to start, process logs and then store the temp files during shrinking. Then open a shell as the user that mirth runs as (you're not running it as root, are you?) and cd in
Post a Comment
Read more

From 0 to ZFS replication in 5m with syncoid

The ZFS filesystem has many features that once you try them you can never go back. One of the lesser known is probably the support for replicating a zfs filesystem by sending the changes over the network with zfs send/receive. Technically the filesystem changes don't even need to be sent over a network: you could as well dump them on a removable disk, then receive  from the same removable disk.
1 comment
Read more

How to automatically import a ZFS pool built on top of iSCSI devices with systemd

When using ZFS on top of iSCSI devices one needs to deal with the fact that iSCSI devices usually appear late in the boot process. ZFS on the other hand is loaded early and the iSCSI devices are not present at the time ZFS scans available devices for pools to import. This means that not all ZFS pools might be imported after the system has completed boot, even if the underlying devices are present and functional. A quick and dirty solution would be to run  zpool import <poolname> after boot, either manually or from cron. A better, more elegant solution is instead to hook into systemd events and trigger zpool import as soon as the devices are created.
Post a Comment
Read more