As far as I know, dyndns gives you an actual DNS lookup, so when someone types your subdomain into their browser, it does a DNS lookup, and gets the IP address you gave to dyndns. That's why port numbers work, it's not that dyndns is listening on every port and forwarding based on the requested subdomain. That being the case, I don't think there's any way to do what you want here: DNS maps names to ip addresses, it doesn't know anything about ports.
I'm not sure how webhop works: you can't tell it to redirect my.domain.com to my.domain.com:8080? Are you only able to give an IP address and port for the destination? If you have legitimate business needs for this site, your best bet is probably to just get a business account with your ISP that will unblock port 80. You'd probably get a static IP with the account, too, so you wouldn't need dyndns, you can just buy a 5$ a year domain name of your own. Plus, additional bandwidth. -Brian On Tue, Sep 30, 2008 at 8:05 PM, <[EMAIL PROTECTED]> wrote: > We are using dydns too. We can append the port number, sure. that sucks for > users though. (thats why we use webhop)maybe we should petition dyndns to > allow the domains they hand out to be linked to an IPADDRESS:PORT instead of > just an IP. That would elminate any workarounds like webhop and suffice to > say solve the port 80 issue with ISP's. > > ----- Original Message ----- From: "Brian Mearns" <[EMAIL PROTECTED]> > To: <users@httpd.apache.org> > Sent: Tuesday, September 30, 2008 2:44 PM > Subject: Re: [EMAIL PROTECTED] Running Multiple Windows Services on port 8080 > > >> How are you "redirecting" to the IP address? I used to use dyndns.com >> for my subdomain name, and I was able to append the port number with >> no problem. E.g., my subdomain was something like bmearns.homeip.net, >> so I just went to http://bmearns.homeip.net:8080. >> >> Do you not want users to see your IP address for security reasons? Or >> just because it's ugly and utterly forgettable? If it's for security >> reasons, and they're connecting directly to your site through the >> domain forwarding (i.e., not through a proxy), then they should be >> able to get your IP address anyway with a DNS lookup. >> >> -Brian >> >>>> [EMAIL PROTECTED] wrote: >>>>> >>>>> John, >>>>> >>>>> We too are limited to port 8080. since our ISP blocks port 80. Have you >>>>> ever found a work around for this? We currently have to have our domain >>>>> [sub.domain.com] redirect to 72.x.x.x.:8080 in order for it to work. >>>>> Now >>>>> users see the ip address in the browser address bar. not good. not good >>>>> at >>>>> all. >>>>> >>>>> Apache 2.2.9 >>>>> Linksys Gateway/Router WCG200 >>>>> >>>>> Jay >> >> --------------------------------------------------------------------- >> The official User-To-User support forum of the Apache HTTP Server Project. >> See <URL:http://httpd.apache.org/userslist.html> for more info. >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> " from the digest: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: [EMAIL PROTECTED] > " from the digest: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
