71 points

If we didn’t have a bazillion TLDs these days we’d be ok and everyone can carry on using .local or .lan and be happy that they’re not real TLDs. Now when anything could be a TLD because every word you’ve ever heard is a TLD, you don’t know if its real or not.

permalink
report
reply
4 points

People have been told for a very long time not to use fake TLDs. I don’t think it’s reasonable to accommodate people who can’t follow instructions.

permalink
report
parent
reply
36 points

Reserved TLDs are documented. The issue is they prioritized all the crazy ones before they added what people at home and businesses were actually using. ICANN won’t sell .lan because it is used too much. They haven’t tried so there is no official decision, but they won’t - they did try .corp and .home and abandoned it.

.local is reserved in RFC 6762, but for multicast DNS.

permalink
report
parent
reply
5 points

They’re documented, but it’s a big and ever expanding list.

permalink
report
parent
reply
5 points

The special use list for use by individuals and business is actually very small and hasn’t been updated in a long time, which is a big part of the problem with people inventing their own.

permalink
report
parent
reply
0 points

I’m sure we’ll keep using .intranet because why should we ever change?

permalink
report
reply
1 point
*

I just use *.loc.al as a local dns entry in my own server with local addresses using devicename.loc.al and loc.al itself going to my gateway/routerpage. 😅

permalink
report
reply
-2 points
Deleted by creator
permalink
report
reply
4 points
*

Don’t follow. Help me out someone please.

The net runs on numbers. The numbers have to be translated into/from the DNS name to the numbers.

Nominating a DNS name as internal is doesn’t change the fact that we still have to, at some stage, find the (local) network mask that that corresponds to.

What am I missing?

Update: I’m not sure I formed my question correctly because I’m none the wiser. That’s my fault, I think.

permalink
report
reply
23 points

It’s for internal resources. You can really use whatever subdomain you want internally, but this decision would be to basically say to registrars, this TLD is reserved, we will never sell this TLD to anyone to use. That way you know that if you use it internally, there’s no way a whoopsie would happen where your DNS server finds a public record for this TLD.

permalink
report
parent
reply
4 points

I assumed that was what .local was all about

permalink
report
parent
reply
3 points

.local is for mDNS addresses.

permalink
report
parent
reply
4 points

A DNS Proxy/Forwarder server? That’s where you would configure how your .internal domain resolves to IPs on your internal network. Machines inside the network make their DNS queries to that server, which either serves them from cache, or from the local mappings, for forwards them off to a public/ISP server.

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

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:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

Community stats

  • 4.9K

    Monthly active users

  • 3.5K

    Posts

  • 75K

    Comments