DNS weirdness

  • Thread starter Thread starter Chris
  • Start date Start date
C

Chris

Hi everyone, I'm a windows DNS newbie, but I've worked
with Unix BIND, so I kind of understand it. Ok here's the
situation:

I have come into an environment that I didn't set up
(sound familiar?) and the client wants to add some domain
names to their current setup and host them. They have
three servers, one that serves as the external DNS
(linux), one that serves as the internal DNS server
(windows 2000 server), and I've added another server that
will only serve as a webserver.

They have an internal and external DNS setup (split) that
answers correctly for the domain names. The problem is
that we have to have port 80 go to one Windows 2000 server
that answers for maindomain.com and I want it to forward
all requests for all other domain names
subdomain.maindomain.com and otherdomain.com to another
server.

Internally, everything works. Externally, the
maindomain.com server answers all requests and doesn't
forward the domains.

Oh and did I mention that the mainserver.com server is a
domain controller, mail exchange, file server, and web
server? LOL... I'm trying to separate these from this one
box, but I'm facing a lot of resistance!

Thanks for the help here!
Chris
 
I have come into an environment that I didn't set up
(sound familiar?) and the client wants to add some domain
names to their current setup and host them. They have
three servers, one that serves as the external DNS
(linux), one that serves as the internal DNS server
(windows 2000 server), and I've added another server that
will only serve as a webserver.
Click to expand...

One key we need to understand: Will these support AD domains
or just Internet published domains names (zones)?
They have an internal and external DNS setup (split) that
answers correctly for the domain names. The problem is
that we have to have port 80 go to one Windows 2000 server
that answers for maindomain.com and I want it to forward
all requests for all other domain names
subdomain.maindomain.com and otherdomain.com to another
server.
Click to expand...

You can't do this with DNS. You must do this with multiple
sites (host headers, IP, or port number) on one server or do
it at the NAT-Proxy server.

NAT routers usually understan just port and address mapping.
Proxies may also understand web requests on port 80 for relay
or mapping to different internal servers.

The simplest way is to acquire multiple public IP address from
the ISP but this isn't always possible (or affordable.)
Oh and did I mention that the mainserver.com server is a
domain controller, mail exchange, file server, and web
server? LOL... I'm trying to separate these from this one
box, but I'm facing a lot of resistance!
Click to expand...

Why? Why separate and if you have good reasons, why
resistance?

One server can certainly do this for a SMALL domain, but
then they might should consider fault tolerance if it goes down.
 
Back
Top