Re: [mh] Linking siteplayer web pages into the Web interface

[Matthew W. <mat...@us...>]

I do a similar thing by running what I believe is a split horizon DNS
system.  Put simply, I use a free DNS service like dyndns.org to resolve
a host name to my external IP when I am in the external network.  For
example:

mh.myname.dyndns.org

In my internal network,  I run my own DNS server which resolves
mh.myname.dyndns.org to an internal IP address instead.  I ensure that
my DNS server only responds to queries from internal IP addresses so
that there is no chance of poisoning the external DNS system.  For
addresses that it doesn't recognize itself, my DNS server either does a
recursive search or asks my ISP's DNS servers to resolve the name for it.

This way, when my web browser tries to resolve mh.myname.dyndns.org, it
gets the right IP address whether it is internal or external.


sam...@op... wrote:
> Hello Ron,
>  Thankyou for your reply.
>    I got it to work on my network at home, but I run into problems when I try to access it from a computer at work (via the internet). I have a public IP address on my router at home and I have some NAT to get to my MH server but when I click on the link to the site player, my browser at work tries to call up the private ip address,  and thats when it fails. 
>   What I really need (I think) is a script that when run, will go and retrieve a web page for you.
> e.g. if you had a link on a MH web page that was something like  getwebpage.pl http://192.168.0.10
> When you clicked on it, the MH server would run getwebpage.pl and the webpage would be retrieved from http:192.168.0.10 and sent to you by the perl script. This way, you could have siteplayers all around your home controlling things, they would be all accessable via the MH server (at full speed on your local network) and also accessable via the internet without any fancy network address translation
>  The main aim being that I can access many webservers, on a private network with private ip addresses, via the internet and also on the private network using one link on a webpage and do it on port 80.
> 
> It's not to much to ask for <BIG GRIN>
> 
> Thanks
> Regards
> Stuart