There are many DNS names options. Which one do you use?

    • masterX244@kbin.social
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      same. saved my ass already a few times when doing some reverseengineering voodoo. being able to set a valid https cert makes it easier to redirect apps than to bypass forced HTTPS. had to pretend to be a update server for something once and patching the URL was enough via getting a cert quickly (using DNS-01 challenge, no exposed ports ever)

  • taladar@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    9
    ·
    1 year ago

    You shouldn’t use .local for your manually defined local domain names if you plan to ever use mdns/avahi/bonjour/zeroconf.

      • Perhyte@lemmy.world
        link
        fedilink
        English
        arrow-up
        6
        ·
        1 year ago

        Hopefully AVM gets to register fritz.box then, because they’ve been setting up their customers with that as their internal domain for ages…

  • KairuByte@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    1 year ago

    *.internal.domain.name since ssl certs are easier to get when you’re using an owned domain name.

  • Still@programming.dev
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    I use either .home or an actual domain that I own (makes it easy for https certs and not having to go out of the network and back in)

  • CAPSLOCKFTW@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I use different ones. Got an legit dpmain which I also use locally (with ssl certificates) and in my local network my server listens to SERVI. Just SERVI.

    • KairuByte@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      While this works for most things, you will run into issues with certain software which automatically assume that no TLD means the provided address is incorrect.

  • iks@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 year ago

    hostname.vlan.local.lan

    local.lan is the only fixed part of my fqdn’s

  • nsaobserverbot@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 year ago

    fritz.box for the machines themselves because Fritz!BOX (although handed out by Pi-Hole),but .lan for anything going over the local proxy towards the same machine for TLS.

    Some machines use my custom domain name instead of .lan, if they need to be accessible from outside. So these last ones go directly over the local proxy internally, but automatically over CloudFlare Tunnel and Authentik when not at home. The proxy being Caddy.