And I got downvoted into oblivion for bringing it up 🤣
Lolwut??? Did you check the GitHub at all?
This is so vibecoded 🤣 Nawthx
Logs
Get a better job so you can afford better drugs. This is “Minimum Wage Methy”, and you want to be “Salaried Methy”.
The failure rate is going to be absolute INSANE as well.
This ONLY works at an insane scale. This will never hit the consumer market.
Gotta say… This is not how you’d generally do any of this. Where you get this info?
Then something has changed about the local deployment and concentration of the network near you. Don’t know what to tell ya 🤷
As long as the provider is the same, and your instances are using properly using DoH or DoT, you have nothing to worry about.
If you’re super concerned though, I’d be using Mullvad over Cloudflare though. Just saying.
See my other response. This is quite normal.
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.
Your public IP is DHCP. It changes from time to time. Nothing weird about that.
Any of the other IP’s in the DNS Servers list changing is just what you get pointed to when resolved based on your GeoIP location.
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.
HA is definitely the largest adopted. OpenHab is probably more geared for developers, but has a more concise and powerful automation system.
As for hardware to run it on: get a cheap n100 Minipc and be done with it. Uses 6-12W, and it’s going to miles.kore efficient for this use than a regular PC.
It’s not the CPU. All that will do is consume CPU and raise your energy bill.
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.
I’ve made a few, but they were quite specific in their purpose. The esp32 ecosystem is pretty great for this purpose, but generally I find people won’t take the time to fuss around with making their own anything when off the shelf varieties are cheap.
You’re describing a CDN. You can’t afford it.
I’d look more into boosting whatever your uplink is versus trying to distribute to localized users.
This is an ad.