- This topic has 1 reply, 2 voices, and was last updated 18 years, 8 months ago by
.
-
Posts
-
We have a small, family company that we run from our home. There are 2 other employees who work from their homes. We want to start using the wiki, calendar, etc to better colaberate with each other. When we set up our xserve, we used a domain that we weren’t using anywhere else. Currently we use dyndns to manage getting back to the xserve, since it is on connection that gets a dynamic ip address.
I have a bunch of custom web redirects set up so things are cleaner then the dyndns hostnames with ports- for the convience of people outside of the local network. Our webserver (www.webserver.com) is hosted elsewhere on the web.
What I have set up is with dyndns:
http://www.domain.com redirects to http://www.webserver.com
group.domain.com redirects to hostname:port#/groups/wikiBoth of these work great outside of our network, but not inside. I understand that this is becouse the xserve is the dns server internally and not able to resolve this, while externally dyndns is the dns server resolving this. Both of these dns server situations I am fine with.
What i want to be able to do is redirect internal requests to external resources. So when an internal request for http://www.domain.com the xserve knows to pass it to the real webserver at http://www.webserver.com. Any help on this would be greatly appreciated.
I’m not 100% clear on what your current configuration is, but from what I was able to gather it sounds like you’re using Apache to cover up a symptom rather than address its cause. Rather than redirecting anything I think you should probably focus on configuring your internal nameserver to provide the same information as the rest of the net–maybe delegate a zone to the dynamic host and/or use a VPN for your remote employees. I do something similar only I use my external web server’s copy of BIND to handle the DDNS updates for me (as opposed to DynDNS) and it works pretty well.
- You must be logged in to reply to this topic.