I'm not primarily a network admin, which is probably why I don't understand how the parts of your answer connect to each other and to the question.

I thought that a static IP was to keep a consistent address on that network. I don't understand how that helps you resolve DNS for outside connections. Is that because you then ignore that network's DNS for everything, including other computer on its subnet?

If you can get an IP address outside of the DHCP range

Is this the static IP you assign yourself? And you need to do this in order to avoid picking an IP that DHCP might assign to someone else, yes? (I've had that happen with a poorly designed VPN product. It was messy.) Or do you mean something else like "get to an IP address outside..."?

When you set a static IP address for a connection (the OS doesn't matter, it's the same everywhere) you configure IP address, gateway, DNS servers and related settings directly on the device. You must configure all of these settings manually, you can't just set an IP address and get the rest from DHCP, it's either one or the other. You need to either be the administrator for the network or get these settings from an admin, otherwise you risk getting a collision if the same IP address is used elsewhere. These settings will then only apply to this specific connection, every other connection that is still set to DHCP will use the settings (including DNS) it gets provided by DHCP. I'll update the screenshot to show more of said settings.