The plan is to keep the world at bay by never recording it in the DNS root – like many already do with a subdomain for an intranet
  • Corngood@lemmy.mlEnglish
    17·
    1 year ago

    Huh, I’ve seen .local used for this quite a bit and only just now realised that it’s meant for something else.

    I’ve also seen .corp 🤮

    • perishthethought@lemm.eeEnglish
      14·
      1 year ago

      And .home.

      Hopefully this .Internal domain takes off and becomes generally recognized as the only correct non-routable domain we all use. Otherwise it’s just the latest addition to the list of possible TLDs and confusion continues.

      • Bitrot@lemmy.sdf.orgEnglish
        31·
        1 year ago

        It’s such a shitty situation. ICANN is not going to sell .home or .corp as they found a crapton of traffic when they checked for it, but IETF never finished an RFC for them - however people easily stumble into the draft RFC that lists what they were thinking of, and assume stuff like .lan is good to go too. They’re safe by ICANN policy, but unsanctioned.

        .home.arpa is safe, per RFC, but user unfriendly to normal people. There are a few others but none a corporation would realistically use. I’ve used . internal for lab testing stuff for ages, so this is extra good news for me I guess.

        Really I wish they’d have just reserved the most common ones rather than getting caught in some bureaucratic black hole.

  • Hexarei@programming.devEnglish
    8·
    1 year ago

    Meanwhile, for my homelab I just use split DNS and a (properly registered+set up) .house domain - But that’s because I have services that I want to have working with one name both inside and outside of my network

  • deadcatbounce@reddthat.comEnglish
    51·
    1 year ago

    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.

    • VelociCatTurd@lemmy.worldEnglish
      18·
      1 year ago

      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.

          • BCsven@lemmy.caEnglish
            2·
            1 year ago

            Can you explaim further: I’m savvy enough to install a custom kernel for a 14 year old arm board and flush drive boot sector with U boot, etc, so I can use it as a dedicated DAAP server, but Networking somehow eludes me

            • VelociCatTurd@lemmy.worldEnglish
              3·
              1 year ago

              Sure. Though I’m not an expert on mDNS or anything. It stands for multi cast DNS. In a normal scenario, when your PC tries to connect to a local resource at its hostname it will use a local DNS server (or its own cache). It’s like a phone book. I know who I’m looking for, I just need to look in the phone book and see what their IP is. With mDNS there is no server. You’ll have a service that will plan to respond at a particular .local hostname, so like jellyfin.local (this is just an example, I don’t know if it has mDNS) but that isn’t registered on a server. Instead when your PC wants to reach jellyfin it will send a multi-cast to the other local devices and say “ok, I’m looking for some guy named jellyfin.local, which one of y’all is that?” And the jellyfin server will respond and say “yo what up, this is my ip address”

              So anyway, that only works with .local addresses. You could use .local with a regular dns server, but then you may run into a conflict. So that would be the benefit of reserving .internal

              • BCsven@lemmy.caEnglish
                2·
                1 year ago

                Thanks this is helpful. So .local hasn’t been reserved for only on local LAN, and .internal would be registered so ot never looks outside of lan?

                • VelociCatTurd@lemmy.worldEnglish
                  2·
                  1 year ago

                  .local is definitely local but it’s common for it to be used with mDNS primarily. To the second part of your question, yes that’s correct, since it will be reserved it will not be any public DNS server, even if it did look outside it wouldn’t find anything.

    • JakenVeina@lemm.eeEnglish
      4·
      1 year ago

      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.