My pleasure - good luck with the implementation. Thanks,
Sam 2009/4/10 Brijesh Deo <[email protected]> > Thanks for clarifying this one too :-) > Yes, I think with one wildcard DNS record, this would work perfectly > fine. > But we also have customers who do not want to add a Domain Name entry > for the reverse proxy server. They would just use the IP address to > access it. And others would add the DNS entry happily. > > So, I am thinking of supporting both the mechanisms in my code and > provide a configuration option to the user letting them use the > mechanism they can support in their environment :) > > Thanks a lot for the help here. Really appreciate your detailed > responses. > > Thanks, > Brijesh > > > -----Original Message----- > From: Sam Crawford [mailto:[email protected]] > Sent: Friday, April 10, 2009 5:14 PM > To: HttpClient User Discussion > Subject: [Junk released by Allow List] Re: How to proxy multiple web > servers? > > Morning, > > Option 1 is most definitely still an option for you. You'd create a > wildcard > dns A record, maybe something like: > > *.devices.company.com => 10.0.0.1 > > So any sub-domain of devices.company.com will resolve to that one IP > address > - which would be your reverse proxy. Then in your reverse proxy you have > some functionality to dynamically support loading of new hostnames. So > the > logic will be all held on the reverse proxy - the DNS just points > everything > at your server. > > You definitely do not need to make DNS changes or local hosts file > changes > for each new device you want to support :-) > > Hope this helps, > > Sam > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
