Let’s start with an example. I own a domain domain.com and have setup plex.domain.com for my Plex instance with cloudflare pointing to my IP and Nginx proxy manager doing the reverse proxy part. Everything is working great and with SSL.

Now if I want to use a domain locally what is the recommended setup and naming scheme for all my machines (server, my PC, printers…) and services(Plex, NAS, cloud, heimdall…)

A records in pi-hole for machines: server.local pointing to 192.168.0.101? Or server.domain.local?

CNAME records for services: in pi-hole for plex.local or plex.server.local pointing to server.local?

Is using .local recomended? or .home, .lan?

Bonus question. I want to upgrade from my old and not updated Owncloud to Nextcloud AIO (seems great, tried years ago the non-AIO version and had performance issues with syncing - maybe corrupted installation or misconfiguration, AIO seems to make this easy). The problem is AIO requires TLS. Easy, cloudflare -> nginx proxy manager -> nextcloud container. Now what if I want to access Nextcloud localy? If I go through cloud.domain.com its slow since it goes through cloudflare.

  • IGC1K@alien.topBEnglish
    1·
    8 months ago

    Hey man, i think we have the exact same setup

    I personally have a dashboard that has has all my services, and it’s on cloudflare for access outside the house, but i set up a dns record pointing to my nginx, and cname records of my websites to the dns record

    And i use the exact same domain and and other stuff

  • McMaster-Bate@alien.topBEnglish
    1·
    8 months ago

    Just run split DNS. Set the same records on your Pi-hole, and they will be used first over external records in Cloudflare. You can go as far as setting a wildcard that points every record under *.domain.com to your reverse proxy (manual entries will override this wildcard) and you will then just have to add an entry point to your reverse proxy and they’re ready to go.