🚀 go-pugleaf

Hi everyone

Ive got a question that maybe someone could help me with? Im trying to get
past some routing issues in my current network setup. Heres what ive got::

1 - Linux Firewall and DNS server/internet gateway with 1 static ip
(204.210.193.x)  and 1 internal ip (192.168.1.1)  (on seperate nics). All
the machines on my private lan (listed below) use this DNS server (im using
IP chains packet filtering)

1 - Windows 2000 Web server running SQL server and Oracle 8 (private ip of
192.168.1.3)
1 - Solaris 8 File/Web and Email server (may reinstall this so i can use
oracle 8 on it) (private ip of 192.168.1.4)
1 - Windows 2000 Pro/Win 98/Gnome work station machine for my development
and everyday use (private ip of 192.168.1.5)

My linux machine is a registered primary DNS server @ internic for two
domain names i purchased a while ago. What id like to achieve is have either
of my domain names route to seperate machines behind my firewall/gateway
machine. For example www.marvelous3.com should go to the Windows 2000
machine on my private IP address 192.168.1.3 and www.y2khub.com should go to
the solaris machine on ip addy 192.168.1.4

Web is just a start. I will also need FTP access to the machines but i'll
worry about that later. Ive looked into port forwarding but i cant get past
the problem of wanting to redirect SOME of the traffic to one machine and
some to another.
Plus Im not sure if thats even the correct path to go on since both of the
domains are routed to the  DNS server.

(NOTE TO TERMINOLOGY ENTHUSIASTS: I beg your forgiveness if im using the
wrong terms here. My understanding and the way im accustomed to setting up
internet machines is with DNS and all the machines usually have static IP's.
(ohhh back in the dayyyyyyy) :) Any machines with private lan addresses
would never be running internet services. I apologize if im confusing
'routing' and 'resolving')

Basically Im pretty much stuck at how to get the DNS requests to resolve
where i need them on my private lan. I understand there are security issues
to think about but again first things first :) Ive been banging my head up
against this for a while as most of the documentation ive come across
describes machines with static IP's behind firewall configs OR single
gateway machines running Web/ftp or email services.  I also  may just be
completely  on the wrong track here as well since im not an expert  by any
means.

 I would really appreciate any help/guidance or insight into this matter

Thanks in advance
-Terry
techlord@mailroom.com