up vote 1 down vote favorite
share [g+] share [fb]

Here's the deal: I have multiple machines on my network which I'd like to make externally accessible via a dynamic DNS service. In the past, I've simply made one machine available via router-based dynamic DNS support and port-forwarding. Is there a way to run a daemon on each machine rather than on the router and effectively have one machine accessible via a.mydynamicdns.com and the other via b.mydynamicdns.com?

The reason I ask is because it would seem that this would be impossible, due to the fact that both machines share the same public-facing IP address (which is dynamic). Is this possible at all? If not, is there a way to accomplish what I'm talking about?

link|improve this question
81% accept rate
feedback

3 Answers

up vote 1 down vote accepted

Sure it's possible. It's just redundant. And I can't be certain that a single Dynamic DNS provider would support it (you might have to use two, like noip.org and dyndns.org (I think they are organizationally different). What you end up with is two names pointing to the same IP. Since your router can only forward one port to one IP, it won't matter - if you forward RDP to one name and VNC to another, for example, BOTH names will respond to both requests, but only the PCs where the ports are forwarded to will answer.

Put another way, the Dynamic DNS clients are JUST pointing an IP to a name and don't care how your router is configured or what services are available on your systems.

link|improve this answer
But this pretty much defeats the whole purpose of having two DNS names, as they point to the same IP. I'd like two separate DNS names, with port 80 going exclusively to one machine per DNS name. Is there a way to do that? – TK Kocheran Jun 20 '11 at 21:01
2  
@TKKocheran Not without two public IPs. You can do some interesting stuff on your router side, such as forward 80 to computerA:80 and 81 to computerB:80, but ports from a single public IP can only be assigned once. If you want to serve different HTTP websites for different domains, then look into VirtualHosts, but that only works for websites. – Darth Android Jun 20 '11 at 21:15
Suppose I'm running a Linux router. Is there a way to redirect to the proper computer based on requested domain name, like an Apache VHost? – TK Kocheran Jun 21 '11 at 19:56
feedback
up vote 0 down vote

For port 80 if one of the machines is running apache2 (and online all the time) you can use proxy pass to fowrward win.example.com to the (internal) ip of your iis server


ProxyPreserveHost On
ProxyPass / http://192.168.111.2/
ProxyPassReverse / http://192.168.111.2/
ServerName win.example.com

(taken from the Using Virtual_host and mod_proxy together example at http://httpd.apache.org/docs/2.0/vhosts/examples.html)

Mod_proxy is advertised as "This module implements a proxy/gateway for Apache. It implements proxying capability for FTP, CONNECT (for SSL), HTTP/0.9, HTTP/1.0, and HTTP/1.1. The module can be configured to connect to other proxy modules for these and other protocols." so it should work slightly more than port 80.

link|improve this answer
This wasn't specifically an Apache question, more of a general question, as I'd like to provide other services too, such as SSH, FTP, etc. – TK Kocheran Jun 21 '11 at 17:44
In order to make it work with "any" service a reverse proxy is what I would use. (see for instance wiki.squid-cache.org/ConfigExamples/Reverse/VirtualHosting for squid documentation and examples) – Jontas Jun 21 '11 at 19:23
feedback
up vote 0 down vote

Yes it is possible - you can use two accounts as an example on the server side and that would work just fine. Use account 1on machine A and account 2 on machine B.

There are plenty of free ddns providers to choose from such as those at:

Dynamic DNS

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.