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.

Comments

Popular posts from this blog

Indexing Apache access logs with ELK (Elasticsearch+Logstash+Kibana)

Who said that grepping Apache logs has to be boring?

The truth is that, as Enteprise applications move to the browser too, Apache access logs are a gold mine, it does not matter what your role is: developer, support or sysadmin. If you are not mining them you are most likely missing out a ton of information and, probably, making the wrong decisions.
ELK (Elasticsearch, Logstash, Kibana) is a terrific, Open Source stack for visually analyzing Apache (or nginx) logs (but also any other timestamped data).

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.

A not so short guide to TDD SaltStack formulas

One of the hardest parts about Infrastructure As Code and Configuration Management is establishing a discipline on developing, testing and deploying changes.
Developers follow established practices and tools have been built and perfected over the last decade and a half. On the other hand sysadmins and ops people do not have the same tooling and culture because estensive automation has only become a trend recently.

So if Infrastructure As Code allows you to version the infrastructure your code runs on, what good is it if then there are no tools or established practices to follow?

Luckily the situation is changing and in this post I'm outlining a methodology for test driven development of SaltStack Formulas.

The idea is that with a single command you can run your formula against a matrix of platforms (operating systems) and suites (or configurations). Each cell of the matrix will be tested and the result is a build failure or success much alike to what every half-decent developer of…