• deadcatbounce
    link
    fedilink
    English
    3
    edit-2
    5 months 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.world
      cake
      link
      fedilink
      English
      145 months 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.

    • @JakenVeina@lemm.ee
      link
      fedilink
      English
      35 months 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.