DNS routing question

I have one static IP with my DSL ISP (Frontier). Due to having to
upgrade DSL modem/router in order to "help" Frontier make a circuitry
upgrade to their system I lost some functionality in my router (I had to
take out of service a 3com 812). The feature that I liked in the 812
was a built in DNS server that allowed me to route different domains to
different in-house IPs on my internal LAN.

Now that I have this new modem/router, it does not have the internal DNS
server. Currently I am mapping all traffic to my main server running
Red Hat 9 (inhouse IP 192.168.200.40). I want to be able to route some
web traffic to another box (let's call it .41), but I don't want to
route mail traffic from .40 for that domain. (I could, but I don't want
to.) How can I set up DNS (or apache virtual hosts for that matter) to
do this? I'm not finding any HOW-TO's or the like that help me. In a
perfect world, I'd want to route http and ftp and/or SSH to the new box.
Mail could be left on the original server. Another part to this would
be, could I run the DNS routing on the original box (.40) or would I
have to add another box in between my modem and the internal net?

I have looked at FREESCO, but that doesn't seem to help either.

Thanks in advance for any pointer on this.

Jim

"Jim Johnston" <(E-Mail Removed)> wrote in message
news:cTjkf.325$(E-Mail Removed)...

>I have one static IP with my DSL ISP (Frontier). Due to having to upgrade
>DSL modem/router in order to "help" Frontier make a circuitry upgrade to
>their system I lost some functionality in my router (I had to take out of
>service a 3com 812). The feature that I liked in the 812 was a built in
>DNS server that allowed me to route different domains to different in-house
>IPs on my internal LAN.

> Now that I have this new modem/router, it does not have the internal DNS
> server. Currently I am mapping all traffic to my main server running Red
> Hat 9 (inhouse IP 192.168.200.40). I want to be able to route some web
> traffic to another box (let's call it .41), but I don't want to route mail
> traffic from .40 for that domain. (I could, but I don't want to.) How
> can I set up DNS (or apache virtual hosts for that matter) to do this?
> I'm not finding any HOW-TO's or the like that help me. In a perfect
> world, I'd want to route http and ftp and/or SSH to the new box. Mail
> could be left on the original server. Another part to this would be,
> could I run the DNS routing on the original box (.40) or would I have to
> add another box in between my modem and the internal net?

I'm confused. What does DNS have to do with anything? This sounds like
port forwarding.

DS

David Schwartz wrote:


>
> I'm confused. What does DNS have to do with anything? This sounds like
> port forwarding.
>
> DS
>
>

I don't want to port all http traffic for all domains to the second
server... just certain ones. I agree, if that were the case, it would
be port forwarding, and the router always does not.

"Jim Johnston" <(E-Mail Removed)> wrote in message
news:cTjkf.325$(E-Mail Removed)..

> I have one static IP with my DSL ISP (Frontier). Due to having t
upgrad
> DSL modem/router in order to "help" Frontier make a circuitr
upgrade t
> their system I lost some functionality in my router (I had to tak
out o
> service a 3com 812). The feature that I liked in the 812 was
built i
> DNS server that allowed me to route different domains to differen
in-hous
> IPs on my internal LAN
>
> Now that I have this new modem/router, it does not have the interna
DN
> server. Currently I am mapping all traffic to my main serve
running Re
> Hat 9 (inhouse IP 192.168.200.40). I want to be able to route som
we
> traffic to another box (let's call it .41), but I don't want t
route mai
> traffic from .40 for that domain. (I could, but I don't want to.)
Ho
> can I set up DNS (or apache virtual hosts for that matter) to d
this
> I'm not finding any HOW-TO's or the like that help me. In a perfec
> world, I'd want to route http and ftp and/or SSH to the new box
Mai
> could be left on the original server. Another part to this woul
be
> could I run the DNS routing on the original box (.40) or would
have t
> add another box in between my modem and the internal net
>
I'm confused. What does DNS have to do with anything? This sound
like
port forwarding

D

On Sat, 03 Dec 2005 18:15:11 +0000, Jim Johnston shouted Hoy......

>
>
> David Schwartz wrote:
>
>
>>
>> I'm confused. What does DNS have to do with anything? This sounds like
>> port forwarding.
>>
>> DS
>>
>>
>
> I don't want to port all http traffic for all domains to the second
> server... just certain ones. I agree, if that were the case, it would
> be port forwarding, and the router always does not.

Then maybe your looking for apache to do URL rewriting?

--
Dancin' in the ruins tonight
mail: echo onub-(E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
Tayo'y Mga Pinoy

(E-Mail Removed)lid (David Schwartz) writes:

>"Jim Johnston" <(E-Mail Removed)> wrote in message
>news:cTjkf.325$(E-Mail Removed)...

>> I have one static IP with my DSL ISP (Frontier). Due to having to
>upgrade
>> DSL modem/router in order to "help" Frontier make a circuitry
>upgrade to
>> their system I lost some functionality in my router (I had to take
>out of
>> service a 3com 812). The feature that I liked in the 812 was a
>built in
>> DNS server that allowed me to route different domains to different
>in-house
>> IPs on my internal LAN.
>>
>> Now that I have this new modem/router, it does not have the internal
>DNS
>> server. Currently I am mapping all traffic to my main server
>running Red
>> Hat 9 (inhouse IP 192.168.200.40). I want to be able to route some
>web
>> traffic to another box (let's call it .41), but I don't want to
>route mail
>> traffic from .40 for that domain. (I could, but I don't want to.)
>How
>> can I set up DNS (or apache virtual hosts for that matter) to do
>this?
>> I'm not finding any HOW-TO's or the like that help me. In a perfect
>> world, I'd want to route http and ftp and/or SSH to the new box.
>Mail
>> could be left on the original server. Another part to this would
>be,
>> could I run the DNS routing on the original box (.40) or would I
>have to
>> add another box in between my modem and the internal net?
>>
> I'm confused. What does DNS have to do with anything? This sounds
>like
>port forwarding.

Agreed. Your system has a single external IP address, let me say it is
11.22.33.44

You want a connection from the outside world coming to 11.22.33.44:25 to be
directed internally to 192.168.1.40, but a connection from the outside
coming to 11.22.33.44:80 you want directed to 192.168.1.41:80
Is this what you want?

That is port forwarding.
And many routers are capable of port forwarding.
This has nothing to do with dns. In fact dns would be useless. they would
look up the number 192.169.0.41 say, but that cannot be routed outside your
network.

Now, there is also the issue internally. You can just use the hosts file
instead of setting up a whole internal dns, unless you have a hundred or
more computers internally.


One point is that your ISP is highly likely to, without warning, filter out
all port 25 or port 80 incoming traffic. (incoming email and http are too "dangerous")

Unruh wrote:


>> I'm confused. What does DNS have to do with anything? This sounds
>>like
>>port forwarding.
>
>
> Agreed. Your system has a single external IP address, let me say it is
> 11.22.33.44
>
> You want a connection from the outside world coming to 11.22.33.44:25 to be
> directed internally to 192.168.1.40, but a connection from the outside
> coming to 11.22.33.44:80 you want directed to 192.168.1.41:80
> Is this what you want?
>

NO, this is not what I want.

I want say http://www.xxx.com to go to .40 and www.yyy.com to go to .41
in house. Both would be from 11.22.33.44 on the outside. But I can
live with mail to be routed all to .40.

I'm already using port forwarding (and filtering) in the modems built in
NAT server to route http/ftp/ssh/mail/https to the .40 box. If it
helps, the modem/router Frontier supplies is a Speedstream 5930 by
Siemens (which their own techs tell me is a piece of poopie compared to
the 3Com 812 I originally bought).

> That is port forwarding.
> And many routers are capable of port forwarding.
> This has nothing to do with dns. In fact dns would be useless. they would
> look up the number 192.169.0.41 say, but that cannot be routed outside your
> network.
>
> Now, there is also the issue internally. You can just use the hosts file
> instead of setting up a whole internal dns, unless you have a hundred or
> more computers internally.
>

So, which file (hosts file) would this be that you are talking about?
Would this work in conjunction with named?

>
> One point is that your ISP is highly likely to, without warning, filter out
> all port 25 or port 80 incoming traffic. (incoming email and http are too "dangerous")
>
This isn't a residential line... I have had a business class line with
them for about 4 years, so this type of filtering better not happen.

On Sat, 03 Dec 2005 21:41:39 +0000, Jim Johnston shouted Hoy......

[putulin]

>>
>> Agreed. Your system has a single external IP address, let me say it is
>> 11.22.33.44
>>
>> You want a connection from the outside world coming to 11.22.33.44:25 to be
>> directed internally to 192.168.1.40, but a connection from the outside
>> coming to 11.22.33.44:80 you want directed to 192.168.1.41:80
>> Is this what you want?
>>
>
> NO, this is not what I want.
>
> I want say http://www.xxx.com to go to .40 and www.yyy.com to go to .41
> in house. Both would be from 11.22.33.44 on the outside. But I can
> live with mail to be routed all to .40.

Then you want to have a look at this
Traffic from the outside going to .40 with www.yyy.com going to .41 using
mod_rewrite under apache. The .40 box apache w/mod_rewrite then sends
www.yyy.com to .41

See: http://httpd.apache.org/docs/2.0/misc/rewriteguide.html

[putulin]

--
Dancin' in the ruins tonight
mail: echo onub-(E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
Tayo'y Mga Pinoy

Baho Utot wrote:


> Then you want to have a look at this
> Traffic from the outside going to .40 with www.yyy.com going to .41 using
> mod_rewrite under apache. The .40 box apache w/mod_rewrite then sends
> www.yyy.com to .41
>
> See: http://httpd.apache.org/docs/2.0/misc/rewriteguide.html
>
> [putulin]
>

Thank you all for the help... combining all of your suggestions, I've
been able to make things work!

On Sun, 04 Dec 2005 01:00:25 +0000, Jim Johnston shouted Hoy......

>
>
> Baho Utot wrote:
>
>
>> Then you want to have a look at this
>> Traffic from the outside going to .40 with www.yyy.com going to .41 using
>> mod_rewrite under apache. The .40 box apache w/mod_rewrite then sends
>> www.yyy.com to .41
>>
>> See: http://httpd.apache.org/docs/2.0/misc/rewriteguide.html
>>
>> [putulin]
>>
>
> Thank you all for the help... combining all of your suggestions, I've
> been able to make things work!

I just knew we had an answer to your problem ;^)

I am glad it worked out for you.

--
Dancin' in the ruins tonight
mail: echo onub-(E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
Tayo'y Mga Pinoy