Okay, so if that’s your actual DNS Server, can you confirm that it works? dig @yourdns debian.org, for example. Afterwards try to use the default DNS of your system dig debian.org. If both works, your DNS config should be fine. Try a curl debian.org -v too.

debian.org is just a random domain for this, use whatever you want. I don’t see anything badly configured so far.

Okay, no external software for DNS management present here. Is that ip a working DNS Server? Is it your server itself perhaps?

From the output, you don’t have any routing rules for your machine that block outgoing traffic. The dig command confirms that you can talk to servers. 9.9.9.9 is a common DNS Server. Based off of this, it seems like your problem is that your system has a bad DNS configuration (it’s always DNS).

Can you parhaps cat /etc/resolv.con? This file normally contains the used DNS servers for Linux systems, unless using special software.

Can you dig @9.9.9.9? If so, its certainly DNS. If it’s not DNS, perhaps try to check your iptables iptables -L && iptables -t nat -L.

Good news, hope the Turks get that idiot out of the office.

Bin Pfälzer, kenne ich nicht.

Wofür steht RND?

Sounds pretty good! I use jellyfin, so regular music players are not really needed for me most of the time (that is everything except downtime), but when still on the local side, I too found Elisa not to have the full experience

I’m on vacation. No working. Well, actually I was doing a ton of Selfhosting stuff (migrating my homeserver to proxmox, now at a usable level), but also video games.

The wordle-analyzer will have to wait until next week, and until I can fix my lifetime compiler errors in the latest commit, and before that: Until I fix my forgejo server that refuses to start after updating the server kernel.

Good to hear, I’ve only been in the Linux World for a few years myself, but I was very surprised too. Through I don’t think that using cp is any different in terms of creating boot records and a partition table.