I'm not clear how far towards your goal, you've got, so apologies for asking obvious questions, but I'll start at the end, and work backwards.
1) Can you ssh email@example.com
2) can you ssh myname@
3) can you nslookup hostname.mydomain.com and get
4) can you ping
5) if you traceroute how close do you get?
5.1) do you get as far as the remote side of the tunnel
5.2) did you get past the local site of the tunnel
I may be telling grandma how to suck eggs, but setting up vpn, is a 3 stage process.
1) set up the tunnel, either with either end creating the tunnel on some traffic event, or up permanently
2) ensure all the traffic that enters the tunnel leaves it with an address, that's identifiable by whats going to receive it (in your case the NATing server, but that means remote servers can't initiate conversations with your machine)
3) ensure that traffic that gets out of the remote side of the tunnel, can reach it's destination, and get back again. For this reason, I normally setup ICMP echo first, and leave it up, so I can check this stage, first, if I have any problems.
Just remember traceroute is your friend, and you will most likely need routing setup correctly, to get from each machine to the next. NAT complicates that, hence when I last setup a VPN myself, I ensured the private networks on both sides of the tunnel had different network addresses and could route between each other (in my case I had 192.168.A.x and 192.168.B.x and 192.168.C.x all bouncing off of a single publicly facing server, where each had to NAT from a different web location, to access the internet. That meant it was much easier, to tell each local DHCP server, to add routes, to the other networks, via the local entry point to the tunnel).
Hope that helps, sorry if it's just stating what you already knew.