Selfhosted

You don't need a local DNS server to set up https, but you do need a domain name. If it's something that you wanted to pick up, you can buy them at a number of different places and you'd have to set up a mechanism to make sure the IP address referenced is the correct one. You can either do that by having a static IP address or by setting up some form of dynamic DNS. Then you can use letsencrypt to set up https.

Okay so here's I think the core of your question though: the only way that someone outside of your network can access your nextcloud is if you have set up the server to be accessible from the outside world. You would have to go into your router and forward Port 80 to the local IP address of your nextcloud server. If you don't do that, then it will only be accessible to the people inside of your network. Rotors do something called Network address translation which lets many devices on your local network connect to the internet despite only having one external IP address. If you're accessing the server using a 192.168 address or a 10.x.x.x address you are already using the internal IP address and not your external Internet IP address so you're likely safe.

One neat trick because remembering IP addresses is a pain in the butt is the hosts file. On windows it's in c:\windows\system32\drivers\etc\hosts and you can set a hostname to immediately resolve to a certain IP address. It's particularly nice because it's free, it's fast, and once you set it you can forget it.

My websites are on the public internet, but I use the host to file to point them at the internal IP address because that way I can directly connect to my servers even when the internet is down.