Scrath

I think the Pi 4 was the first Pi with gigabit ethernet. All the Pi's before that were limited to 100Mbit. For that reason, syncthing is probably a bad idea since it will be very slow in terms of syncing speed

Try debugging a distributed embedded real time system which crashes when you are in a breakpoint too long because the heartbeat doesn't respond

It looks angry

Physical since I carried it over from my old phone which didn't support eSIM.

I did get an eSIM some time ago for a short vacation in switzerland though. The activation went surprisingly smooth even though I had to wait a day before they verified me. The verification delay was probably because I used a foreign ID to register at a swiss provider for that eSIM.

Can definitely confirm this. I started with a Proxmox system which had a TrueNAS VM. TrueNAS just used a USB HDD for storage though. Setting everything up and getting the permissions set correctly so I could connect my computers was a pain in the ass though.

Later I bought a synology and it just works. Only thing I would recommend is getting good HDDs. I bought Toshiba MG08 16TB drives and while they work great, they are obnoxiously loud during read and write operations. They are so loud, that even though the NAS is in a separate room I have to shut it off at night.

Meanwhile the Seagate Ironwolf drive I used for TrueNAS was next to my bed for multiple months and was basically silent.

Thanks for your reply. I think I managed to solve this issue and have updated my post to reflect this. Apparently I had a setting disabled in Pi-Hole which caused my DNS requests to be forwarded upstream for some reason, even though there existed a local DNS entry.

It returned the local IPv4 address of the server and two IPv6 addresses belonging apparently belonging to a cloudflare server in california.

I think I managed to fix the issue though. I have updated my post to include my solution

I think I fixed the issue by enabling the Never forward reverse lookups for private IP ranges option in Pi-Hole. After that I flushed my dns cache again and called tracert for my domain name. I only get one hop directly to my server now. nslookup also shows only local addresses now.

Outside hosting isn't really something I want to consider. I didn't mention this in my post but this setup is for my media server which needs a lot of storage space. I don't know about the pricing for a VPS but I am pretty sure it isn't as cheap as I would want it. Also uploading my media to a VPS with my upload rate would take a lot of time whenever I want to add something new.

Using two hostnames for accessing the same service isn't really an option either unfortunately. The specific part I'm trying to set up is a navidrome server for music. The app I use to access the server is called Symfonium and can only add one address per media server. I could get around that by adding multiple media sources but that would result in all of my media appearing twice in searches.

Looking at the output of that command I get the following for my ethernet network interface

DNS-Server  . . . . . . . . . . . : fd98:1919:5915:0:3053:4134:bdc9:295d
                                          192.168.1.60
                                           fd98:1919:5915:0:3053:4134:bdc9:295d

Using nslookup on that IPv4 address tells me that all of those addresses are pointing to my pi-hole

nslookup 192.168.1.60

Server: pi.hole
Address: fd98:1919:5915:0:3053:4134:bdc9:295d

Name: pi.hole
Address: 192.168.1.60

I've added another local DNS entry on my Pi-Hole which points the domain I use to the same server but this time uses its IPv6 address. That doesn't seem to help though or it takes some time to update. I flushed the DNS cache on my machine after adding this entry though.

Do you have a better alternative you can recommend? My upload rate isn't all that good so I would like to avoid having more traffic than necessary leaving my network if the target is within my network anyway.

When I use tracert I can see the package going through a server in Frankfurt which is definetely outside of my local network. The final IP address that tracert shows me is from a cloudflare server in california (2606:4700:3033::ac43:b10f) according to this site: https://whatismyipaddress.com/ip-lookup

Using nslookup for my domain I get 3 addresses. The first two are cloudflare addresses in the US. The final one is my servers local IP address.