> One perk that someone told me about is that you can use your domain to get around not having a static IP (because the DNS will compensate).

No this wont really help you with that. A domain name (‘A’ record in a DNS provider such as Cloudflaire) is simply a pointer to an IP address. If you configure this with a non-static address (e.g. your public IP provided by your ISP) then this will at somepoint change and therefore no longer resolve. You would then need to manually update the IP in the DNS record each time.

There are services you can run locally to automate this update (check on your router) called Dyanmic DNS. DDNS will basically call a configured endpoint to automate the change.

> If I were to get a Cloudflare domain name then what would be some other pros and cons?

Personally I set up an A record to point my domian `mydomain.com` to a local IP (19.168.1.x) which is running NGINX proxy manager. With a wildcard CNAME such as `*.mydomain.com` I can add all my local services in NPM with valid letsencrypt certificates.

Now I never need to use IP’s/ports as I can:

- Access all my local services via valid SSL certs

- Manage them in a single place (NGINX proxy manager)

- Use nice looking URL’s using subdomains (e.g `https://router.mydomain.com`)

- Same with email addresses. I can use `[email protected]` - which I have configured in Cloudflare to forward to my primary gmail account (Just add a `MX` entry).