Selfhosted

60482 readers

777 users here now

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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

502

ICANN approves use of .internal domain for your network (www.theregister.com)

submitted 2 years ago by thehatfox@lemmy.world to c/selfhosted@lemmy.world

148 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Voroxpete@sh.itjust.works 20 points 2 years ago (1 children)

Certain domain names are locally routed only. So if you use internal or local as a tld, you can just assign whatever names you want and your computer won't go looking out on the internet for them. This means you and I can both have fileserver.local as an address on our respective network without conflicting. It's the URI equivalent of 192.168.0.0/16.

[–] torkildr@lemmy.world 5 points 2 years ago

Interesting that you should use ".local" as an example, as that one's extra special, aka Multicast DNS