|
|
|
#1 |
|
Messages: n/a
Hébergeur: |
We're moving our web server from our SBS lan and now am a bit confused.
It's a complete reinstall of WS03 Std. We'll have multiple sites so we need to run hostheaders. Since this machine is outsite our SBS lan, it'll need to be running it's own DNS. It's a stand-alone server and really doesn't need to be a domain controller, or run active directory, well, unless that's the best practice. I was looking for tutorials on just running a simple web server and dns server, but all mention AD or being a DC, etc. I'm willing to bite the bullet and follow the path, but seems silly to have all this for couple of websites. Thanks. Hugh |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
<hughgjohnson@comcast.net> wrote in message
news:1157317702.565751.39860@i3g2000cwc.googlegrou ps.com... > We're moving our web server from our SBS lan and now am a bit confused. > It's a complete reinstall of WS03 Std. We'll have multiple sites so we > need to run hostheaders. Since this machine is outsite our SBS lan, > it'll need to be running it's own DNS. It's a stand-alone server and > really doesn't need to be a domain controller, or run active directory, > well, unless that's the best practice. I was looking for tutorials on > just running a simple web server and dns server, but all mention AD or > being a DC, etc. I'm willing to bite the bullet and follow the path, > but seems silly to have all this for couple of websites. No, if you just look in the you will find plenty of information on setting up a Standard Primary DNS. But your DNS for such public resources almost certainly belongs (back) at the REGISTRAR. For one thing you are suppose to have TWO (minimum) DNS servers for your zones. -- Herb Martin, MCSE, MVP Accelerated MCSE http://www.LearnQuick.Com [phone number on web site] > > Thanks. > > Hugh > |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
Herb,
Thank you. I did see the DNS docs, but there is so much DC and AD sprinkled in it, well, kinda scared me that what I was doing was wrong. We have back up DNS and MX via Dyndns.org so all should be good. Thank you for your . Hugh Herb Martin wrote: > <hughgjohnson@comcast.net> wrote in message > news:1157317702.565751.39860@i3g2000cwc.googlegrou ps.com... > > We're moving our web server from our SBS lan and now am a bit confused. > > It's a complete reinstall of WS03 Std. We'll have multiple sites so we > > need to run hostheaders. Since this machine is outsite our SBS lan, > > it'll need to be running it's own DNS. It's a stand-alone server and > > really doesn't need to be a domain controller, or run active directory, > > well, unless that's the best practice. I was looking for tutorials on > > just running a simple web server and dns server, but all mention AD or > > being a DC, etc. I'm willing to bite the bullet and follow the path, > > but seems silly to have all this for couple of websites. > > No, if you just look in the you will find plenty of information > on setting up a Standard Primary DNS. > > But your DNS for such public resources almost certainly belongs > (back) at the REGISTRAR. > > For one thing you are suppose to have TWO (minimum) DNS > servers for your zones. > > > > -- > Herb Martin, MCSE, MVP > Accelerated MCSE > http://www.LearnQuick.Com > [phone number on web site] > > > > > Thanks. > > > > Hugh > > |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
You definitely do not need AD or DNS to run a webserver (IIS?).
If you have it in a DMZ then you should definitely not have it as a DC or the whole DNS of your company. So why not just make a membersserver and IIS to run the website? If this is to be within your LAN and does not have any special security issues then adding it to the DCs would make life easier (authentification via domain users for example). "hughgjohnson@comcast.net" wrote: > We're moving our web server from our SBS lan and now am a bit confused. > It's a complete reinstall of WS03 Std. We'll have multiple sites so we > need to run hostheaders. Since this machine is outsite our SBS lan, > it'll need to be running it's own DNS. It's a stand-alone server and > really doesn't need to be a domain controller, or run active directory, > well, unless that's the best practice. I was looking for tutorials on > just running a simple web server and dns server, but all mention AD or > being a DC, etc. I'm willing to bite the bullet and follow the path, > but seems silly to have all this for couple of websites. > > Thanks. > > Hugh > > |
|
|
|
#5 |
|
Messages: n/a
Hébergeur: |
<hughgjohnson@comcast.net> wrote in message
news:1157330708.386697.65250@e3g2000cwe.googlegrou ps.com... > Herb, > > Thank you. I did see the DNS docs, but there is so much DC and AD > sprinkled in it, well, kinda scared me that what I was doing was wrong. > We have back up DNS and MX via Dyndns.org so all should be good. > The technical differrence for AD is only that the records are stored in AD instead of in a file on the file system. Of course, you get extra features too, but their aren't really that many of them, they mostly related to replication EFFICIENCY and increased SECURITY (mostly for dynamic registration.) Have you looked at the "DNS Checklist" in the ? -- Herb Martin, MCSE, MVP Accelerated MCSE http://www.LearnQuick.Com [phone number on web site] > Thank you for your . > > Hugh > > > Herb Martin wrote: >> <hughgjohnson@comcast.net> wrote in message >> news:1157317702.565751.39860@i3g2000cwc.googlegrou ps.com... >> > We're moving our web server from our SBS lan and now am a bit confused. >> > It's a complete reinstall of WS03 Std. We'll have multiple sites so we >> > need to run hostheaders. Since this machine is outsite our SBS lan, >> > it'll need to be running it's own DNS. It's a stand-alone server and >> > really doesn't need to be a domain controller, or run active directory, >> > well, unless that's the best practice. I was looking for tutorials on >> > just running a simple web server and dns server, but all mention AD or >> > being a DC, etc. I'm willing to bite the bullet and follow the path, >> > but seems silly to have all this for couple of websites. >> >> No, if you just look in the you will find plenty of information >> on setting up a Standard Primary DNS. >> >> But your DNS for such public resources almost certainly belongs >> (back) at the REGISTRAR. >> >> For one thing you are suppose to have TWO (minimum) DNS >> servers for your zones. >> >> >> >> -- >> Herb Martin, MCSE, MVP >> Accelerated MCSE >> http://www.LearnQuick.Com >> [phone number on web site] >> >> > >> > Thanks. >> > >> > Hugh >> > > |
|
![]() |
| Outils de la discussion | |
|
|