Win2k Web Server

[Podolak]

Ok, I am trying to learn a little about IIS and Exchange. So, what I did was I went out and registered a new domain. I setup IIS on my Windows 2000 Server box with a default page that loads fine internally via the servers IP address. Now what I'd like to do is tie the server to my domain. Any suggestions on how to do this?

Thanks!

 

[Vegito]

bring up another server, any spare box.. better not to use the same as exchange

install w2k and run dcpromo to start the active directory

call the server domain as your domain.com

make your domain controller dns as your domain.com, etc.

you know dcpromo command ? start -> run -> cmd, dcpromo

 

[Podolak]

yeah, the exchange box (which doesn't have exchange on it yet) is the domain controller with the same domain name as the one I registered. I ran dcpromo and did active directory ect. and setup a basic page in IIS. I'm wondering how to tell my web domain to look at my server for the site...

 

[Buddha Bart]

This can be a tricky chicken-egg situation some times.

Go wherever you registered your domain and login. Then try to set the domains nameservers as your IP. Sometime's their picky and will only accept hostnames, not IPs.

bart

 

[watts3000]

Podolak I always prefer to separate my name sapce for example a companies internal domain name my be alphacompany.com. There public dns name will be www.alphac.com.
Also do you palin on running your own dns server. I noticed Buddha Bart stated "Go wherever you registered your domain and login. Then try to set the domains nameservers as your IP. Sometime's their picky and will only accept hostnames, not IPs"
Its not that simple first off you must create a dns server then you must contact the company that you registered your domain nmae with and ask them to register your dns server. If I remember correct you must have a primary and secondary dns server, but you can get around this by signing up for a service like www.zonedit.com. Now you can use your server as primary and one of theres as a backup. Then you must decide on how your dns server will be publically displayed will you put it in a dmz zone or will you simply forward ports to your box on your lan. Also in order to run a website you will have to set the correct a records and if you plain on using your excahnge server to recieve internet mail you will have to set a a record for the box and a mx record. BTW do you have a static ip and are you behind a router. Let me know and I will go further into how to set exchange up.

 

[Podolak]

Its not static but my ISP changes my IP address so infrequently its not going to matter. This is just for me to learn on anyways. I am behind a router and I've already forwarded the IP address of the server so it can get out. I installed DNS last night and if you goto techsrv.net it brings up an old index.html I had laying around from a previous experiment with linux. but www.techsrv.net does not work. I went to zoneedit.com and I registered my site with them and am using their dns servers. In their config I forwarded www.techsrv.net to my ip address but ofcourse they say it takes three days for the dns servers to transfer or whatever so we'll see. I guess they'll be hosting my mx record too I think?

 

[watts3000]

Which dynamic dns client did you use they are all ok but I prefer direct update it runs as a service. It should not take that long check back in a couple of hours. In most cases I have seen it did not take but 4 hours at the most. Also as for as your mx record you will have to set that up you will want to point the mx record to the public ip address of your router. Also check this site out its pretty good for trouble shooting dns http://www.dnsreport.com. Also I will list some cmd line stuff you can do when you start to work on your exchange server.