Hi, I have a DNS question, I think. I've come into an environment that uses a split dns setup and I'm trying to add a couple of domains to the setup. The problem is that the boss doesn't want to add them to the existing server. So I've set up a Linux server that I can add the extra domains to.

Ok here's the problem. We have three servers set up now. One that serves the external DNS. One that is a Windows 2000 server that serves mail and www for domain1.com and the internal DNS. One that I've added that runs subdomain.domain1.com and domain2.com. Now I've been adding the internal DNS records and zone files to the third server and everything works internally. Internally, when you type in domain1.com, you get the correct website. Externally, when you type in domain1.com, you get the subdomain.domain1.com website that's hosted on the third server and not the second server.

The question, am I missing something here? Everything works beautifully when you're on the internal network, but when you look at it outside the network, port 80 pulls up the wrong website. Do I have to add anything to my apache configuration? I just want it to forward to the correct server.

Ok here are the specifics:

----------------------------------
servers
----------------------------------

1. Server 1 - Linux RH 8, serving as the external DNS.
2. Server 2 - Windows 2000 Server serving mail and www for domain1.com
3. Server 3 - Linux RH 8, serving mail and www for domain2.com and subdomain.domain1.com

Thanks for the help!
HD

Ok maybe I should rephrase my question. Is there any way to route based on ip address, port, and domain name? I guess this is basically what I need!

Thanks!
HD

Anyone?

yes there is a way that you can route based on ip address, port, or domain name.
you need to use <VirtualHost> and do the configuration there on the apache server.
I believe the file is on /etc/httpd/confg (check the confg I'm not sure that's the correct spelling) open this file and look for the <VirtualHost> part. you can get more info on this topic going to the apache web site. apache.org and look at the VirtualHost Derective you'll find the info you want

hope this can help you!!

if anything you can write me. matos30@yahoo.com
see ya

Based on the above, this sounds like either your external DNS server is returning the wrong "external" IP address for the new server or your firewall is not redirecting (DNAT) external requests for the new servers external IP address to the proper internal IP address of the new server internally. Long pause... Hope that made sense.

Example:

www.domain1.com = 1.2.3.4 External, 10.10.10.4 Internally
www.domain2.com = 1.2.3.5 External, 10.10.10.5 Internally
and so on

Your firewall would then need to:
DNAT external 1.2.3.4:80 requests to 10.10.10.4:80 internally
DNAT external 1.2.3.5:80 requests to 10.10.10.5:80 internally
and so on

hopefully that makes sense.