As tomcooks said, you can't directly add https to a DNS server address in your settings and have it work.

However some DNS providers support the new standard DNS-over-HTTPS (including Google and Cloudflare). Some also support the alternative new standard DNS-over-TLS (including Cloudflare).

While support for these encryption methods support is offered by some DNS providers, your client devices may or may not support the new encryption methods. Firefox is currently implementing DNS-over-HTTPS so at least Firefox DNS requests will be soon able to use it and Google is currently beginngin to implemen it in Android. The new encryption methods are still in Draft status so expect to see adoption increase as they near completion.

Just using 1.1.1.1 is going to be unencrypted DNS. If you trust cloudflair they claim to delete logs after a short period.

Using DNS over HTTPS which you can leverage in the latest Firefox nightly will make your DNS queries over a HTTPS website service. This will prevent your ISP or anyone else from tracking your DNS queries (besides cloudflare of course).

I am not a sysadmin but you can't add https:// (or any other prefix) in front of a DNS address. Secure HTTP is a different protocol, suited for web page hosting.

DNS Lookup has its own protocol that doesn't work with https. If you send an https request to a DNS server, even if you include all the other parameters required for a DNS lookup, you won't get back a usable response (unless the server has been setup to proxy DNS requests over https, but this comes at a speed cost and increases your server overhead, so it is very uncommon - I've never heard of this happening. edit: apparently 1.1.1.1 supports this)

+1 for asking, though. Nothing wrong with trying to learn more about something you know very little about. Not sure why others are downvoting you.