i am using verizon fios and have attemped to connect to full node. verizon said that i can n0t do it on their router and would need to purchase a 3rd party router and daisy chain to theirs. Any suggestions would be appreciated. thanks.
This may be a good start.
There may be more specific info about configuring a Verizon router on their website.
There are services that allow routing to your node and I believe Verizon routers support using dyn.com and other DNS services - it may be in an advanced configuration tab in the router UI.
It depends on what you are trying to do - but this should point you in the right direction.
To run a full node you don't need to have opened incoming port. It will function correctly being just a "fetching" node.
When you are behind NAT which one you do not manage you still can achieve your node visibility in various ways:
1) Using third party "middleman" services.
as Randy mentioned, there is a dyn.com, where you install their client and then you have a domain, which will be routed to your WAN ip, even it changes all the time. I thought this service solves only dynamic WAN IP change - in this case this won't help you if your provider still is blocking incoming connections (need port forward). but probably they offer also so-called "port tunneling" with their client.
there's also great service by https://ngrok.com/ , you can configure it to access your bitcoind REST api even you are behind filtered NAT.
Be aware that in this case all the data you exchange probably can be read by those service providers (still very unlikely)
2) [RECOMMENDED, most self-controlled and private option] You can use Tor hidden service. The complete guide is available here: https://2019.www.torproject.org/docs/tor-onion-service.html.en . In short: you spin up a tor daemon, and then create so called "tor hidden service", which basically means that you need to set in config some "tor port forwarding".
HiddenServiceDir /var/db/tor/your/local/path/for/particular/onion HiddenServicePort 8333 127.0.0.1:8333 #exposing to TOR network bitcoind communication port HiddenServicePort 8332 127.0.0.1:8332 #exposing to TOR network bitcoind RPC port
/var/db/tor/your/local/path/for/particular/onion directory you can find
hostname file which will be smth like
32j46jh46r4hy45hy435j7h47h4e6yhreu.onion. Then any bitcoin node which is operating via TOR proxy will be able to connect to your node. The advantage of such approach is that you can also use remotely RPC commands in encrypted way (all data transmission is encrypted in TOR)
3) i'll take this question as opportinity to shill my own service https://bitclouds.sh - you can spin up full bitcoin node which will be pre-synced and available on regular internet. Reliable and 24/7 connected, because located in high-grade datacenters. You have full control of such node, it has TORed outgoing connections out-of-box, you are able to RPC remotely (but be aware of risks when allowing remote RPC, its not reccomended and remote calls are not enabled by default on bitclouds - you need to change line in bitcoin.conf). Here's more info: https://github.com/bitcoin-software/bitbsd-clouds/tree/master/bitcoind (non-custodial, keys and configs under your control). Thanks to underlying filesystem (ZFS) i am using i am able to offer such bitcoind "containers" just for 66 sats per hour, so it is even cheaper to run on old PC at home.