

I think needing a VPN to access the internal network is a good practice. And if you’re going to be used a VPN anyway, I don’t see why you wouldn’t use a “fake” TLD like .lan for internal stuff, after all it’s just simple DNS rules.
I think needing a VPN to access the internal network is a good practice. And if you’re going to be used a VPN anyway, I don’t see why you wouldn’t use a “fake” TLD like .lan for internal stuff, after all it’s just simple DNS rules.
not OP, but feedly is quite privacy invasive. the content you read is very valuable data, self hosting keeps your reading interests private.
I’m more of a prosody enjoyer but the guide seems to be well written and your website looks great! really refreshing compared to those corporate copycat blogs.
come on, setting up your own DNS is not difficult at all. For my home network, it’s running in a Raspberry Pi, but before that I ran it locally on my desktop. There’s no way I’d spend 15$ a year to resolve internal addresses.
Sure, you have to be careful with the TLD you choose, but I believe that if the ICANN were to create the .lan TLD, it would be all over the internet first.