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
  • MystikIncarnate@lemmy.caEnglish
    1·
    9 months ago

    I have clients that use internal, but they do it as a subdomain; so internal.contoso.com

    Any internal only domains that I set up are probably going to go the same way. I’ve used domain.local previously, and the DNS headache I get from that is immeasurable.

    With so many things going “to the cloud” or whatever, the internal.domain.tld convention tends to make more sense to me.

    What’s everyone else doing?

  • Possibly linux@lemmy.zipEnglish
    1·
    10 months ago

    Please no

    It would be nice to figure out a way to get local SSL certs for .lan and .local domains though.

  • theit8514@lemmy.world
    1·
    10 months ago

    If only they had done this with .local ages ago. Still, it’s a nice change, but I doubt my company will adopt.

    • LordCrom@lemmy.world
      1·
      8 months ago

      .local is a bad choice especially if you have any MAC hosts on the network.

      There is an RFC about that, but I’m too sleepy to goook it up

    • Pup Biru@aussie.zone
      1·
      10 months ago

      .local exists for a very specific reason and it’s not meant to be used by regular DNS… people use it for alternate things, but it’s reserved for mDNS

      if .internal were to be added, we could start using that instead of overloading!