same. saved my ass already a few times when doing some reverseengineering voodoo. being able to set a valid https cert makes it easier to redirect apps than to bypass forced HTTPS. had to pretend to be a update server for something once and patching the URL was enough via getting a cert quickly (using DNS-01 challenge, no exposed ports ever)
While this works for most things, you will run into issues with certain software which automatically assume that no TLD means the provided address is incorrect.
fritz.box for the machines themselves because Fritz!BOX (although handed out by Pi-Hole),but .lan for anything going over the local proxy towards the same machine for TLS.
Some machines use my custom domain name instead of .lan, if they need to be accessible from outside. So these last ones go directly over the local proxy internally, but automatically over CloudFlare Tunnel and Authentik when not at home. The proxy being Caddy.
I use different ones. Got an legit dpmain which I also use locally (with ssl certificates) and in my local network my server listens to SERVI. Just SERVI.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
server.home for my part
I use a subdomain of a domain name I own.
*.internal.domain.namesince ssl certs are easier to get when you’re using an owned domain name.hostname.vlan.local.lan
local.lan is the only fixed part of my fqdn’s
I just bought an actual domain and use that 😅
As an added bonus, letsencrypt works with no effort.
same. saved my ass already a few times when doing some reverseengineering voodoo. being able to set a valid https cert makes it easier to redirect apps than to bypass forced HTTPS. had to pretend to be a update server for something once and patching the URL was enough via getting a cert quickly (using DNS-01 challenge, no exposed ports ever)
Idk is that wrong but I made up server name tride so .tride is my local domain
.home.lan for me.
nothing as home does work (meaning plain hostname) works by default on openwrt dns
While this works for most things, you will run into issues with certain software which automatically assume that no TLD means the provided address is incorrect.
Usually adding a slash at the end works if the protocol is http based
fritz.box for the machines themselves because Fritz!BOX (although handed out by Pi-Hole),but .lan for anything going over the local proxy towards the same machine for TLS.
Some machines use my custom domain name instead of .lan, if they need to be accessible from outside. So these last ones go directly over the local proxy internally, but automatically over CloudFlare Tunnel and Authentik when not at home. The proxy being Caddy.
I use different ones. Got an legit dpmain which I also use locally (with ssl certificates) and in my local network my server listens to SERVI. Just SERVI.