Win2K Adv Srv, Single IP, multiple web sites, DNS

  • Thread starter Thread starter Cliff
  • Start date Start date
C

Cliff

I have a Win 2K Adv Srv running AD and want to host multiple WEB Sites on
this server with one IP. Here's what I have accomplished thus far:

I setup the Server as a DC named crpoe.

I installed AD.

I built the WEB Site and added the host header and assigned the IP of the
server.

I called Network Solutions and had the domain name pointed to my IP.

When I type the URL, I am expecting it to go to the web site on my server,
to which I believe I have pointed the requests based on host header.
However, this is not working.

I feel sure I need to do some more with DNS and I am currently reading the
knowledgebase for details and was hoping for some help from here as well.

What steps are left for me to do?

Thanks,

Cliff
 
Cliff said:
I have a Win 2K Adv Srv running AD and want to host multiple WEB Sites on
this server with one IP. Here's what I have accomplished thus far:
Click to expand...

These are two separate issues and should be treated as such even though it
is
completely feasible to do it with one piece of hardware.

Making it publicly available on the Internet entails some security issues
though.
I setup the Server as a DC named crpoe. I installed AD.

I built the WEB Site and added the host header and assigned the IP of the
server.

I called Network Solutions and had the domain name pointed to my IP.
Click to expand...

Probably a bad idea. Leave the PUBLIC DNS with your registrar. For
many reasons, not least of which is that you apparently don't have a second
server to run a "shadow" or "split" DNS -- use the registrar's DNS server
for the public side of the split.

Other reasons: They will provide multiple DNS servers as it expect on the
Internet. They have 24-7 support. The world has NO business seeing your
internal DNS.
When I type the URL, I am expecting it to go to the web site on my server,
to which I believe I have pointed the requests based on host header.
However, this is not working.
Click to expand...

So you real problems are in the records at the DNS server -- did you setup
the DNS server to contain these records?
I feel sure I need to do some more with DNS and I am currently reading the
knowledgebase for details and was hoping for some help from here as well.
Click to expand...

Add the A or Host records.
What steps are left for me to do?
Click to expand...

Here's what you should really do:
Have the Registrar put the PUBLIC DNS (registration at .Com or wherever)
back to THEIR server (if they have a self-service web page where you can
set
your own records -- if not, then move to another registar such as
Register.com
where you CAN do this.)
Add the PUBLIC A records to that public DNS server.

Install DNS on your DC (you did this)
Specify that it should ONLY handle requests on the INSIDE address
(the world-of-the-Internet will use your Registrar's DNS server)
Turn on SECURE Dynamic updates ONLY -- you aren't going to expose
the DNS server to the world (outside address) but "stuff" happens.
Add those SAME records you added to the public server AGAIN on this
internal server. (They aren't going to replicate so you must do
this each
time you add or change a public address or name within your zone.)
Add any other INTERNAL static records (printers, older machines or
anything
that won't register itself dynamically)
DO NOT add these internal records to the public server at the
Registrar.

Point all CLIENTS to the internal address of this internal server -- the DC
itself is
an INTERNAL client.

Enjoy.
 
I have a Win 2K Adv Srv running AD and want to host multiple WEB Sites on
this server with one IP. Here's what I have accomplished thus far:

I setup the Server as a DC named crpoe.

I installed AD.

I built the WEB Site and added the host header and assigned the IP of the
server.

I called Network Solutions and had the domain name pointed to my IP.

When I type the URL, I am expecting it to go to the web site on my server,
to which I believe I have pointed the requests based on host header.
However, this is not working.

I feel sure I need to do some more with DNS and I am currently reading the
knowledgebase for details and was hoping for some help from here as well.

What steps are left for me to do?
Click to expand...

See:

Running mutiple web sites on a single IP address:
http://www.iisanswers.com/Top10FAQ/t10-hostheaders.htm
http://www.iisanswers.com/articles/dns_for_iis.htm

Jeff
 
In Cliff <[email protected]> posted a question
Then Kevin replied below:
: I have a Win 2K Adv Srv running AD and want to host multiple WEB
: Sites on this server with one IP. Here's what I have accomplished
: thus far:
:
: I setup the Server as a DC named crpoe.
:
: I installed AD.

If this is only used for hosting websites, adding AD to the mix only
complicates the issue. Web servers should be only on standalone or member
servers unless you have absolutely no other choice.

:
: I built the WEB Site and added the host header and assigned the IP of
: the server.
:
: I called Network Solutions and had the domain name pointed to my IP.

What does this statement mean?
a. The "A" record for www with your public IP
b. The "A" record for your domain name(Blank) with your public IP
c. The DNS server on this machine?

Answers
a. you also need a www "A" record in your local domainname.com zone with the
internal IP of the website.
b. You need a blank "A" record in your local domainname.com zone with the
internal IP of the website.
c. You need another DNS server to host the public zone on so the records in
the DC's DNS server can point to internal IPs so you can access the sites
from your LAN.

:
: When I type the URL, I am expecting it to go to the web site on my
: server, to which I believe I have pointed the requests based on host
: header. However, this is not working.

You still need a record in an internal DNS pointing to the internal IP of
the website if the webserver is behind NAT.

:
: I feel sure I need to do some more with DNS and I am currently
: reading the knowledgebase for details and was hoping for some help
: from here as well.
:
: What steps are left for me to do?

You have to clarify the first portion of my reply before I can give you
clear instructions.
 
Ever feel like you're in over your head?

OK, Herb, here's the deal...

I installed AD because in addition to hosting my web sites (three small
personal) I have Exchange 2000 running for e-mail.

I have called Network Solutions and they agree on the DNS and it has been
pointed back to their name servers (another 24 to 36 hours to wait).

Under IIS, I created another WEB Site, set the IP to my server's IP, and
added the hostheader to match the URL of the web site. Now, after
propogation, I am expecting someone to type in the URL, be directed to my
router, which will direct the port 80 request to my server, which will
direct the request to the appropriate folder containing the WEB site of the
URL. How am I doing thus far?

Here's what you should really do:

Have the Registrar put the PUBLIC DNS (registration at .Com or wherever)
back to THEIR server (if they have a self-service web page where you can set
your own records -- if not, then move to another registar such as
Register.com where you CAN do this). (DONE)

Add the PUBLIC A records to that public DNS server. (Network Solutions said
they'd add A records for WWW and MX records for mail)

Install DNS on your DC (you did this) (YES)

Specify that it should ONLY handle requests on the INSIDE address (the
world-of-the-Internet will use your Registrar's DNS server) (HOW?)

Turn on SECURE Dynamic updates ONLY -- you aren't going to expose the DNS
server to the world (outside address) but "stuff" happens.

Add those SAME records you added to the public server AGAIN on this internal
server. (They aren't going to replicate so you must do this each time you
add or change a public address or name within your zone.) (getting over my
head...explain more...)

Add any other INTERNAL static records (printers, older machines or anything
that won't register itself dynamically

Point all CLIENTS to the internal address of this internal server -- the DC
itself is an INTERNAL client. (HOW?)

I guess I'm looking for detailed notes on what I need to do now.
 
I forgot to mention that Exchange 2000 is running as well, hence AD.

I'm am learning that I had not setup A records or MX records and have since
let the Registrar handle DNS for me. The registrar also offered to setup A
records and MX records for me since I'm doing mail and web hosting.

At this point, I am waiting for the new DNS to propogate, then I'm expecting
things to work better. I have built an additional web site under IIS and
added the URL as host header. How does this sound thus far?
 
In Cliff <[email protected]> posted a question
Then Kevin replied below:
: I forgot to mention that Exchange 2000 is running as well, hence AD.

OK< well then it makes sense, then. You gotta have AD.

:
: I'm am learning that I had not setup A records or MX records and have
: since let the Registrar handle DNS for me. The registrar also
: offered to setup A records and MX records for me since I'm doing mail
: and web hosting.
OK, so the registrar is handling your public DNS, good choice.

Now, you also know that you need a DNS zone for each of the domains you
host?
You don't need MX records (MX records are only for other mail servers) but
you do need at least one host pointing to the internal IP of the web server.

In the AD zone the web server should already have an "A" host record and
Exchange should also have its record. If they are on the same box you will
only have one "A" for it. Accept if it is also a DC then you will have a
blank (same as parent folder) "A" host.
addomainname.com
Name Type Data
webserver A <webserverip>
exchange A <exchangeip>
(same as parent folder) A <DCipaddress>

For all other domains that you host website for you need a zone for each and
at least this record(one of the few times I recommend CNAMES.)
domain1.com
Name Type Data
www alias webserver.addomainname.com

Exchange will also need a host header for its public FQDN if you plan on
using OWA
You can alias it to the Exchange server IP
:
: At this point, I am waiting for the new DNS to propagate, then I'm
: expecting things to work better. I have built an additional web site
: under IIS and added the URL as host header. How does this sound thus
: far?

So far, so good but you shouldn't need to wait on propagation.
You should have immediate access since you should be using the internal DNS
server, which is required in AD. Just create a zone for each hosted domain
with the records I stated above.
 
In the AD zone the web server should already have an "A" host record and
Exchange should also have its record. If they are on the same box you will
only have one "A" for it. Accept if it is also a DC then you will have a
blank (same as parent folder) "A" host.
Click to expand...


You lost me there...am I setting up these zones in DNS or AD?
 
In Cliff <[email protected]> posted a question
Then Kevin replied below:
: In the AD zone the web server should already have an "A" host record
: and
:: Exchange should also have its record. If they are on the same box
:: you will only have one "A" for it. Accept if it is also a DC then
:: you will have a blank (same as parent folder) "A" host.
:
:
: You lost me there...am I setting up these zones in DNS or AD?

Actually I was referring to the AD Domain forward lookup zone.
 
Got it...and it works. I've learned to do the WEB Sites...not I'm moving on
to Exchange and the e-mails that go with the domains. Thank you for all the
help.

Cliff
 
Back
Top