• 10 Posts
  • 1.31K Comments
Joined 3 years ago
cake
Cake day: July 7th, 2023

help-circle



  • Yes, that’s called Round-Robin Load Balancing.

    To get more specific, your DNS provider spins up a large number of DNS resolvers out in the world on a CDN network that resolves clients to the most geographically convenient server(s) at any point in time based on the GeoIP info of your public IP.

    Once you resolve one set of addresses at any given time, it caches your request, so the next time you ask these DNS servers for something you’ll get a response right back from them as fast as possible.

    You constantly checking is just going to show this. It’s quite normal.


  • You’re going out of your way to prove some unnecessary point with this solution though.

    Only the RPi5 has PCIe, first of all, and the older boards would need a slow USB interface for any type of larger storage. Then you have longevity and reliability questions because of the age of the boards…it’s just worth it.

    OP wants a simple solution. RPi of any kind just ain’t it when you get down a simple list of Pros v Cons list.





  • I might be misunderstanding, but you’re checking what exactly for DNS leaks?

    If the IPs are changing, that’s not uncommon. The HOST changing would be though, like if you swapped from what you expected back to Comcast or something.

    You need to get better control of your local network and not have to be paranoid about this. Static reservations for long lived hosts, your router should have a setting to override and prevent internal hosts (like guests) from sending OoB DNS requests, and any sort of VPS stack should as well.


  • The downvotes here are from people who have no idea what in the world actually works best, and just FEEL a certain way about things 🤣

    Kinda the mantra of this entire sublem.

    I’m honestly not even talking about a Minipc. I’m talking a cheap ass dual bay NAS. Let’s do a price breakdown:

    • RPi5/8GB: $135
    • m.2 dual hat +case with active cooling: $75 (saves a bit)
    • 2x 512GB OR 1TB: $200 / $300
    • 45W Power supply: $50

    So at the bare minimum that’s going to be $460 or $510 for the 1TB variant per device. Then you need to fuck with all the software side of things as well.

    • Synology DS223j 2xbay: $200
    • 2x 4TB HDD: $200

    $400 and you’re done. All the software is ready to go, you’ll have automatic rebuilds of your array if you need to swap drives, and a simple interface to work with everything in.

    I’m not even here simping for Synology, because QNAP and others have similarly priced solutions. I’m here pushing for SIMPLICITY and cost effective solutions.


  • If you’re going for reliability, and you just want things to be simple, you probably just want to spend the money on two cheap NAS boxes, honestly. There are some caveats that come with RPi’s, and you’re unfamiliar it’s: 1) going to cost about the same, 2) be simpler to manage and upgrade, and 3) be easier to repair disk columes when the time comes.

    Even if you’re just looking to make these redundant to each other, just make it simple and easy.




    1. Get some sort of resource monitor running on the machine to collect timeseries data about your procs, preferably sent to another machine. Prometheus is simple enough, but SigNoz and Outrace are like DataDog alternatives if you want to go there.
    2. Identify what’s running out of control. Check CPU and Memory (most likely a memory leak)
    3. Check logs to see if something is obviously wrong
    4. Look and see if there is an update for whatever the proc is that addresses this issue
    5. If it’s a systems process, set proper limits

    In general, it’s not an out of control CPU that’s going to halt your machine, it’s memory loss. If you have an out of control process taking too much memory, it should get OOMkilled by the kernel, but if you don’t have proper swap configured, and not enough memory, it may not have time to successfully prevent the machine from running out of memory and halting.


  • When talking about media streaming, there’s a number of other things that cause problems Bandwidth, meaning the total amount of information you can send overall, is less likely to be a problem versus jitter, packet loss, and latency spikes.

    For this purpose, but OP would tune both the server and the clients to cache ahead more, or send in smaller packets, it could possibly be a good workaround.

    Spending an insane amount of money putting what I’m guessing is illegally obtained content on a CDN distribution is crazypants.