Route *.domain.com to local network?

[zer0hp]

Hello,

I've been lurking for quite a while jsut reading and whatnot, and I finally have an issue.

Scenario: we are an ultrasmall company with an ultrasmall network. We have AT&T DSL at the office with a WRT54GL router running DD-WRT, and a Windows 2003 Server box for AD. I forward LAN DNS requests to the AD box for resolution. Our simple network is a 192.168.1.1 class C network.

We have an extra domain name laying around, and we want to forward that to a particular server on our private network. For example: I want forward all requests to dev1.testdomain.com and dev2.testdomain.com from the internet to particular servers on our private network.

I created a name server entry, ns.testdomain.com, pointing to the static IP address of our DSL and I already set the name server of testdomain.com to ns.testdomain.com. Where do I go from here? How do I get the Windows AD box to understand and route the traffic accordingly?

Is this even possible? Thanks, all.

 

[RebateMonger]

What kind of services are you trying to provide on the additional servers? Web, FTP, or ?? Can you use non-standard ports for these services?

If the additional servers aren't for public consumption, you might find a VPN easier to set up. It could be done with the hardware and software that you already possess.

Publishing mutliple servers using a single IP address can also be done with a proxy server, like Microsoft's ISA 2004/2006. It reads the host header of the inbound request and routes the request to the appropriate server on your internal network.