I'm not sure I can see a way for this to work. I think you may need some
sort of web-proxy or gateway to redirect HTTP requests to the virtual
hosts based on their FQDN.
Once the web address has been resolved to an IP address, that IP address
will be contacted and netfilter will not be aware of the difference
between somebody requesting thisdomain.tld or thatdomain.tld from the
same IP.
Unless there's a netfilter module that I don't know about (quite
possible) that does that kind of HTTP packet inspection, I think you'll
need to redirect the traffic at the application level.
Howard Lowndes wrote:
I know about BIND views, in fact I use them, but I don't think they will
work here.
What I need is for lannet.com.au, thisdomain.tld and thatdomain.tld to
all resolve to the same public w.x.y.z externally, but be DNAT'd to
different private 192.168.y.z addresses internally.
Chris Deigan wrote:
On Tue, 2006-02-14 at 12:44 +1100, Howard Lowndes wrote:
What my problem is: how do I set up DNS so that externally
thisdomain.tld and thatdomain.tld both point to the same external IP
address, but internally they point to different internal IP addresses.
Check out BIND views.
You can setup bind using views so that clients from, say, 172.16.0.* see
your internal zones and everyone else sees external zones.
-Chris.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
