![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
maybe I'm missing something but why would he need anything special? He doesn't need DNS to do this (well kind of, but...), he doesn't need a proxy for sure. All he needs is to have port forwarding turned on and configured properly on his router. Also, why in the world would you want your SVN box open to the world? For SVN, I'd setup VPN, and VPN in when ever you wanted to check-in or out code while remote. The only reason you'll need DNS is to separate your webmail address from your IIS server, otherwise POP and/or IMAP can automatically be pointed to your email server with port forwarding. Look into port forwarding, this is actually pretty simple to setup and nearly every router out there has it (in one form or another).Couple things, it depends on how he's using SVN, if he's actually using SVN then it's on port 3690 so all 443 requests could be directed to webmail. Along that same line, like I said, why in the world would he have his SVN open to the world? Unless he has some type of publicly shared project then there is no reason to have your SVN open to the world, if he is doing a public project he'd be better off using Sourceforge.net since he doesn't understand the most basic parts of web hosting/forwarding. I understand everyone needs to start somewhere (and I applaud those that want to try) but open your code to the world is nuts.
Like I said, forward port 80 to www (private IP) and 443 to webmail (Private IP). If he really insists then point 3690 to svn (Private IP).Couple things, it depends on how he's using SVN, if he's actually using SVN then it's on port 3690 so all 443 requests could be directed to webmail. Along that same line, like I said, why in the world would he have his SVN open to the world? Unless he has some type of publicly shared project then there is no reason to have your SVN open to the world, if he is doing a public project he'd be better off using Sourceforge.net since he doesn't understand the most basic parts of web hosting/forwarding. I understand everyone needs to start somewhere (and I applaud those that want to try) but open your code to the world is nuts.
EDIT: I will say, I've never seen or heard of Pound before, it looks like an interesting/cool project. I've always used hardware devices if I had situations that called for it (like a Big IP). I may download Pound and play around with it, thanks for the link
Sorry, don't kid yourself...it's web facing, it's NOT secure
First rule of security, if someone wants in bad enough, they will get in. Having code exposed to the world (that's not meant to be) is not something I'm ever willing to do.