I’m curious as to why someone would need to do that short of having a bunch of users and a small office at home. Or maybe managing the family’s computers is easier that way?

I was considering a domain controller (biased towards linux since most servers/VMs are linux) but right now, for the homelab, it just seems like a shiny new toy to play with rather than something that can make life easier/more secure. There’s also the problem of HA and being locked out of your computer if the DC is down.

Tell me why you’re running it and the setup you’ve got that makes having a DC worth it.

Thanks!

  • Xakuterie@dormi.zoneEnglish
    2·
    9 months ago

    If I remember correctly that is best practise, no? It was something.local or *.intern for years, until TLDs could be whatever you wanted them to be.

    • nottelling@lemmy.worldEnglish
      1·
      9 months ago

      .local is reserved for mDNS responses, don’t use that.

      It’s more than best practice. Your active directory controllers want to be the resolvers for their members, separate from other zones such as external MX records or the like. Your AD domain should always be a separate zone, aka a subdomain. “ad.example.com”.

      If your DCs are controlling members at the top level, you’ll eventually run into problems with Internet facing services and public NS records.

    • taladar@sh.itjust.worksEnglish
      1·
      9 months ago

      Do not use made up domains for anything these days. It will make it a pain if you ever need a certificate for that domain that isn’t self-signed.