Verizon tends to distribute their modems with routers built into them, a modem/router combo. Typically a router -> router set-up will cause a double NAT issue that will result in making it very damn hard to forward ports. However most modem/router combos enable you to bridge them, meaning they no longer act like routers(thus no longer mess with your ports). This is what you should do with your Verizon router if you haven't.

As for a static IP, you shouldn't need one from your ISP if you set up your router correctly. Just go into your Windows network settings and assign your network a static ip(192.168.2.20 is what mines is). This means whenever your desktop connects to your router then you will always connect with that IP. This is mandatory for you to properly forward ports anyways. Once you have this static ip to your router set up then you should be able to set up a dns with dyndns.org, as a properly set up dyndns will update with a new ip.

From what I'm gathering though, dyndns charges... you can look into alternatives like openDNS, and specifically their client updaters(that keep track of your ever-changing ip): http://www.opendns.com/support/dynamic_ip_downloads/

I have no first-hand experience with this stuff though, just general knowledge on the subject. So breaking it down
1) bridge your verizon modem
2) properly static ip your hosting machine(your desktop) to your router
3) set up an openDNS or something with a client updater