I’ve wanted to install pihole so I can access my machines via DNS, currently I have names for my machines in my /etc/hosts files across some of my machines, but that means that I have to copy the configuration to each machine independently which is not ideal.

I’ve seen some popular options for top-level domain in local environments are *.box or *.local.

I would like to use something more original and just wanted to know what you guys use to give me some ideas.

  • ellipsoidalellipsoid@alien.topBEnglish
    2·
    10 months ago

    “.home.arpa” for A records.

    I run my own CA and DNS, and can create vanity TLDs like: a.git, a.webmail, b.sync, etc for internal services. These are CNAMEs pointing to A records.

  • ohuf@alien.topBEnglish
    2·
    10 months ago

    RFC 6762 defines the TLDs you can use safely in a local-only context:

    *.intranet
    *.internal
    *.private
    *.corp
    *.home
    *.lan

    Be a selfhosting rebel, but stick to the RFCs!

      • Diligent_Ad_9060@alien.topBEnglish
        1·
        10 months ago

        https is not a problem. But you’ll need an internal CA and distributed its certificate to your hosts’ trust store.

  • Spare_Vermicelli@alien.topBEnglish
    1·
    10 months ago

    maybe not directly answer for you, but I just literally bought 4 domains for 3 euro per year (renews at the same price!) 5 minutes ago :D.

    The catch - it has to be 9 numbers.xyz (see https://gen.xyz/1111b for details).

  • tech_medic_five@alien.topBEnglish
    1·
    10 months ago

    lastname. systems

    I used to own lastname.cloud and foolishly let that expire. Its one of my biggest regrets.

  • Mint_Fury@alien.topBEnglish
    1·
    10 months ago

    I use .lan for anything local and my public domain is .net for anything publicly hosted.

  • jerwong@alien.topBEnglish
    1·
    10 months ago

    I use >!.cunt!< for my local TLD. Stands for Can’t Use New Technologies from IT Crowd.

    It makes it comnical when I let friends onto my wifi.

  • certuna@alien.topBEnglish
    1·
    10 months ago

    .local is mDNS - and I’m using that, saves me so much hassle with split-horizon issues etc.

    I also use global DNS for local servers (AAAA records on my own domain), again, this eliminates split-horizon issues. Life is too short to deal with the hassle of running your own DNS server.

  • 404invalid-user@alien.topBEnglish
    1·
    10 months ago

    I had problems with .local because it’s used for MDNS and too lazy to figure out how that works so now I just use lan but I also own a .com domain so I have started to use that more

    • Daniel15@alien.topBEnglish
      1·
      10 months ago

      I use *.home.mydomain for publicly-accessible IPs (IPv6 addresses plus anything that I’ve port forwarded so it’s accessible externally) and *.int.mydomain for internal IPv4 addresses.