

Yeah exit nodes can be lots of effort(probably, never ran one) but relay nodes do get issues. Some banks do outright block any nodes that run tor, regardless of the exit node or relay node status.
Yeah exit nodes can be lots of effort(probably, never ran one) but relay nodes do get issues. Some banks do outright block any nodes that run tor, regardless of the exit node or relay node status.
You would need to create a new torrent whenever new files are added or edited. Not very practical for continuous use.
Yeah porkbun is good.
To see how the glue records work, you can run dig +trace example.com
This answer goes into detail how it works behind the scenes.
https://superuser.com/questions/715632/how-does-dig-trace-actually-work
RFC 2606 is your friend ;-)
Their own doc, sure why not.
Any other context where there’s a giant with the same name. No, please at least write it out expanded once.
Two wrongs don’t make a right. I was scratching my head for a few seconds looking at the thumbnail and the title. And even the post body didn’t clarify things. 🤷🏻
I use porkbun.com for my domains, which is excellent, and also has glue record support.
https://kb.porkbun.com/article/112-how-to-host-your-own-nameservers-with-glue-records
The thing you want is “glue records” the upper level server would serve ns1.example.com (this is an approved domain for example use, better to use example.com than making your own example up) as the authoritative name server. Then provide the glue record which says “ns1.example.com is at IP address X”.
It should ask for IP addresses as well as hostname. Otherwise they only assumed people will “host” their domain in another hosted, as opposed to self-hosting.
In that case (and in any other case) change your registrar to someone else who supports glue records.
Instead of a bare metal hypervisor, you can install Kubernetes on it, k3s works on a single node. Lots of use across the industry.