Your eu.cc domains are fine. You don’t need to spend money on a 2nd-level domain if you’re happy with the longer name.
For comparison, I’ve had a nl.eu.org domain for decades, and never had any issues. I also had a number of .tk domains for a while and those all went away when the business managing the domain got sued out of existence. I currently use nom.es domains for various tests.
You never know. I thought Devuan was a fantasy but the team’s burning hatred was enough to make it work. ¯\_(ツ)_/¯
Ah great. It looks like you have a mostly empty encrypted partition with LVM on top of it. If memory serves you might be able to resize the logical volume and the ext4 filesystem in a single command.
I prefer file systems that checksum data. Without this it is difficult to know when there has been corruption. I generally use brtfs for this reason.
An almost inevitable result of venture capital, IMHO.
I mean, you can get rid of NAT and subnet your systems in a logical fashion. That’s pretty awesome.
I use ULA for my WireGuard tunnels, otherwise it’s all public IPv6 (mostly lightly firewalled).
I’m fine with SLAAC, even for servers. I just manually update my DNS with the server addresses when I set them up.
I give money to LibreOffice, Thunderbird, Armbian, the Wikipedia, and so on. I don’t have to, but it shows my appreciation, and maybe helps them do more in some small way.
Very minor note. The blog mentions that the attacker was unlikely to have gained anything by Monero mining. However the Monero page itself says:
Monero can be mined by both CPUs and GPUs, but the former is much more efficient.
I got 135 blocks via sshguard over the first 12 hours today. So, yeah, welcome to the Internet! 😄
Kubernetes storage is the reason I was looking at Minio in the past.
There’s a bit about those on the Wikipedia:
There used to be restrictions on a hostname.
These had to start with and end with a letter or number, and have only letters, numbers, or a dash. (I heard that originally hostnames had to start with a letter, but 3M got that changed. This might be an urban legend.)
That’s a common restriction for a name still.
Things get funky when you want non-ASCII names - like if you want a cyrillic or Greek name - as registries often limit the allowed characters to limit “isomorphic attacks”. That’s where you use symbols that look the same to trick people into thinking they’re going to another site, like using a 0 instead of an O, or a l instead of an I.
None of this will apply to the XYZ domains that give you a number.
One other issue that might impact you is if you try to connect using only a numeric name. Some tools will interpret such a name as an IPv4 address. Easily solved by using the full name, but weird and confusing if it happens to you unexpectedly. 😅
Seems like someone already did this:
https://github.com/netdata/netdata/issues/20565
Maybe upgrading will fix it?
Self reply as a follow up.
I use nom.es for DNS experimentation. These are like $3 a year or so, and work fine.
I miss DotTK, which was dodgy and didn’t support DNSSEC, but was actually free. 😅
I would not expect any issues.
From the point of view of DNS, a name is a name.
You can never tell what weird restrictions any given software is going to place on you (there were a lot of forms that did not like TLD with more than 4 characters, 20 years ago or so). But it’s only $1, so worth experimenting, IMHO.
Please let us know if there are problems!
All I do:
I think that’s it. I have my host exposed to the Internet. As far as I know, it’s fine.
BTW, sshguard is for the IMAP and SMTP that run on the host, which do allow password logins. But it helps reduce load from brute force attacks on port 22 (which are pointless anyway).
I’m much more worried about my son installing dodgy Minecraft mods, or my wife installing another app that she saw on TikTok. I really should put them each on a separate VLAN…
I’m old school, and would set up Fetchmail. It can pull down either POP or IMAP (I haven’t used POP in 25+ years, but I guess it works fine still). Then I’d run Dovecot or some other IMAP server on my host to read mail from there.
DNS is never the Domain Name Service.
The very first sentence of RFC 1034, the document that is the basis of DNS, identifies it as the Domain Name System.
Using some very basic security, like minimal services and keeping stuff patched and having backups, and you’re probably fine. I’ve run stuff locally at home for decades and never had a security issue as far as I know. (I did have a problem with a hosted server that I shared with some friends 20 years ago, because at that time updating Fedora was a hassle and we let it get behind on updates.)