> I'm also tired of remembering ports, if there's a way of mapping those. Should I run a local proxy?

If we're talking web-services - absolutely. I put Caddy in front of everything just to be able to simply use domains. You can also use it to map ports to either standard or more convenient ones if that suffices. Configuring reverse-proxy with Caddy [0] takes just a few lines:

  http://some-service.internal {
      reverse-proxy localhost:12345
  }

- DNS-server: most routers can be that; another easy option would be PiHole.

- DHCP-server: same as above (PiHole does DHCP too).

- Reverse-proxie(s): you can have either just one for the entire network or a number closer to the amount of services if you choose to have HTTPS between everything. Wouldn't bother with Nginx for that unless there is a strong incentive.

- ACME-server: provides the certs for the local reverse-proxies if you choose to have HTTPS between everything. Caddy can also act as a very easy to set up ACME-server [1].

If you have all that set up, you can access all the local services securely and via readable URLs. Given all the services get their certs from the ACME-server, the consumers only need to trust (install) one root cert in order to consider all the local connections secure.

Might seem like a lot at first, but the configuration is fairly straightforward and I found it's worth the effort.

[0]: https://caddyserver.com/docs/caddyfile/directives/reverse_pr...

[1]: https://caddyserver.com/docs/caddyfile/directives/acme_serve...