Web Edition come with DNS services?

A

April

If I purchase the low-end WEB EDITION version of Windows 2003 Server, does
it come with DNS services? IOW, can I use it to run a domain name server?
 
C

Coraleigh Miller

Web edition does not allow Active Directory services to be used, this
includes dns. Its pretty much just for Web server usage. :)
http://www.microsoft.com/technet/windowsserver/evaluate/features/compare.mspx


Coraleigh Miller

"April" <hostsafe_at_symbol_hotmail_period_com@this_is_my_email_address.com>
wrote in message news:eyaOgkaGIHA.5584@TK2MSFTNGP03.phx.gbl...
> If I purchase the low-end WEB EDITION version of Windows 2003 Server, does
> it come with DNS services? IOW, can I use it to run a domain name server?
>
 
M

Meinolf Weber

A

April


> Web edition does not allow Active Directory services to be used, this
> includes dns. Its pretty much just for Web server usage. :)

Well, can't the argument be made that web servers need a DNS server to
return the appropriate IP addresses for web domain names? You can't run a
web server without a DNS server somewhere linking the domain with an IP.
 
C

Coraleigh Miller

Websites do need DNS to be accessible yes, however many website owners use
external DNS hosting companies to handle this for a very minimal cost
(~$10-$20 per year). Alternatively if you wished to provide your own DNS
service for you website, you could purchase the full Windows Server 2003
Standard edition.. or Windows Server Small Business Edition is a less
expensive alternative and along with DNS provides a few nice extra
components. -give it a look though to see if this is a better fit for you..
http://www.microsoft.com/windowsserver2003/sbs/evaluation/default.mspx

Coraleigh Miller

"April" <hostsafe_at_symbol_hotmail_period_com@this_is_my_email_address.com>
wrote in message news:u0jRuyaGIHA.280@TK2MSFTNGP03.phx.gbl...
>
>> Web edition does not allow Active Directory services to be used, this
>> includes dns. Its pretty much just for Web server usage. :)
>
> Well, can't the argument be made that web servers need a DNS server to
> return the appropriate IP addresses for web domain names? You can't run a
> web server without a DNS server somewhere linking the domain with an IP.
>
 
L

Leythos

In article <eiB1s4bGIHA.5328@TK2MSFTNGP05.phx.gbl>,
coraleighmiller@yahoo.com says...
> Websites do need DNS to be accessible yes, however many website owners use
> external DNS hosting companies to handle this for a very minimal cost
> (~$10-$20 per year). Alternatively if you wished to provide your own DNS
> service for you website, you could purchase the full Windows Server 2003
> Standard edition.. or Windows Server Small Business Edition is a less
> expensive alternative and along with DNS provides a few nice extra
> components. -give it a look though to see if this is a better fit for you..
> http://www.microsoft.com/windowsserver2003/sbs/evaluation/default.mspx


Why would anyone want a public web server to also handle public DNS?

DNS servers should be in the LAN, web servers in the DMZ, if your web
server needs DNS resolution, setup a firewall rule to allow DNS (TCP 53)
from DMZ to LAN IP OF DNS Server.


--

Leythos
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam999free@rrohio.com (remove 999 for proper email address)
 
R

Ryan Hanisco

As some other have pointed out, DNS services are not included with this
version of Windows Server. Generally only very large companies should be
running their own DNS for instances where they are hosting or providing
extranet services.

Generally, you are in a much better position to use the redundancy that a
DNS provider can give you and let your web servers run the web site.

As a matter of clarity, you should generally keep external DNS in your DMZ
and completely separate from your internal DNS. Your hosting environment
should stay well segmented from your internal services to protect both your
data and your site.
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
http://www.techsterity.com
Chicago, IL

Remember: Marking helpful answers helps everyone find the info they need
quickly.


"April" wrote:

> If I purchase the low-end WEB EDITION version of Windows 2003 Server, does
> it come with DNS services? IOW, can I use it to run a domain name server?
>
>
>
 
D

DevilsPGD

In message <MPG.218eff20e2bd343e989741@adfree.Usenet.com> Leythos
<void@nowhere.lan> wrote:

>In article <eiB1s4bGIHA.5328@TK2MSFTNGP05.phx.gbl>,
>coraleighmiller@yahoo.com says...
>> Websites do need DNS to be accessible yes, however many website owners use
>> external DNS hosting companies to handle this for a very minimal cost
>> (~$10-$20 per year). Alternatively if you wished to provide your own DNS
>> service for you website, you could purchase the full Windows Server 2003
>> Standard edition.. or Windows Server Small Business Edition is a less
>> expensive alternative and along with DNS provides a few nice extra
>> components. -give it a look though to see if this is a better fit for you..
>> http://www.microsoft.com/windowsserver2003/sbs/evaluation/default.mspx
>
>
>Why would anyone want a public web server to also handle public DNS?
>
>DNS servers should be in the LAN, web servers in the DMZ, if your web
>server needs DNS resolution, setup a firewall rule to allow DNS (TCP 53)
>from DMZ to LAN IP OF DNS Server.

If you're talking internal LAN DNS, then you're quite correct.

However, if you're talking about an internet facing web server, you need
some sort of DNS service too. This is very often outsourced to your
domain registrar, but there is no practical reason why you need to, if
you have a reasonably skilled DNS admin kicking around and have needs
that exceed your domain registrar's abilities, then it's a very common
and very valid setup.

As it turns out, Windows 2003 Web's DNS server is perfectly capable of
handling this role.

--
You can get more with a kind word and a 2x4 than just a kind word.
 
D

DevilsPGD

In message <593687D8-5413-4671-96A4-9BAE683C7722@microsoft.com> Ryan
Hanisco <RyanHanisco@discussions.microsoft.com> wrote:

>As some other have pointed out, DNS services are not included with this
>version of Windows Server.

Incorrect, however, depending on your needs.

DNS works great in registry or file mode on a Windows 2003 web server,
it simply does not interface with Active Directory.

This is an important distinction, since if you were looking to run a
Windows 2003 Web server for an internet rather then intranet site, this
may be all the DNS you need.

--
You can get more with a kind word and a 2x4 than just a kind word.
 
L

Leythos

In article <vh7bi35lcv05thpin67346hra839m5dr8t@4ax.com>,
spam_narf_spam@crazyhat.net says...
> In message <MPG.218eff20e2bd343e989741@adfree.Usenet.com> Leythos
> <void@nowhere.lan> wrote:
>
> >In article <eiB1s4bGIHA.5328@TK2MSFTNGP05.phx.gbl>,
> >coraleighmiller@yahoo.com says...
> >> Websites do need DNS to be accessible yes, however many website owners use
> >> external DNS hosting companies to handle this for a very minimal cost
> >> (~$10-$20 per year). Alternatively if you wished to provide your own DNS
> >> service for you website, you could purchase the full Windows Server 2003
> >> Standard edition.. or Windows Server Small Business Edition is a less
> >> expensive alternative and along with DNS provides a few nice extra
> >> components. -give it a look though to see if this is a better fit for you..
> >> http://www.microsoft.com/windowsserver2003/sbs/evaluation/default.mspx
> >
> >
> >Why would anyone want a public web server to also handle public DNS?
> >
> >DNS servers should be in the LAN, web servers in the DMZ, if your web
> >server needs DNS resolution, setup a firewall rule to allow DNS (TCP 53)
> >from DMZ to LAN IP OF DNS Server.
>
> If you're talking internal LAN DNS, then you're quite correct.
>
> However, if you're talking about an internet facing web server, you need
> some sort of DNS service too. This is very often outsourced to your
> domain registrar, but there is no practical reason why you need to, if
> you have a reasonably skilled DNS admin kicking around and have needs
> that exceed your domain registrar's abilities, then it's a very common
> and very valid setup.
>
> As it turns out, Windows 2003 Web's DNS server is perfectly capable of
> handling this role.

If you can only afford that cheap version of Windows, with limited CPU
support, then my guess is that you're not actually going to purchase a
quality firewall device, proper configuration, and you're going to cheap
out on other things. There is no reason to be running your own public
facing DNS on your Web server also - it's just another point of exposure
to be attacked.

Yes, it "Can" be done, not it's not a best practice.

--

Leythos
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam999free@rrohio.com (remove 999 for proper email address)
 
D

DevilsPGD

In message <MPG.218f71a02ed456c3989743@adfree.Usenet.com> Leythos
<void@nowhere.lan> wrote:

>> If you're talking internal LAN DNS, then you're quite correct.
>>
>> However, if you're talking about an internet facing web server, you need
>> some sort of DNS service too. This is very often outsourced to your
>> domain registrar, but there is no practical reason why you need to, if
>> you have a reasonably skilled DNS admin kicking around and have needs
>> that exceed your domain registrar's abilities, then it's a very common
>> and very valid setup.
>>
>> As it turns out, Windows 2003 Web's DNS server is perfectly capable of
>> handling this role.
>
>If you can only afford that cheap version of Windows, with limited CPU
>support, then my guess is that you're not actually going to purchase a
>quality firewall device, proper configuration, and you're going to cheap
>out on other things. There is no reason to be running your own public
>facing DNS on your Web server also - it's just another point of exposure
>to be attacked.
>
>Yes, it "Can" be done, not it's not a best practice.

Sure, that makes sense. I always spend as much money as possible when
buying licensing to ensure that I get extra features I know I won't
need. I like knowing I can install 16 CPUs, even if the hardware only
has one socket, and having support for 8GB of RAM even though the
intended application will run fine on 1GB-2GB of RAM, and that's all we
intend to install.

Is it a good solution for everyone? Obviously not. However, if you're
only running a small to medium web server, and don't need to exceed the
CPU, RAM, or other licensing restrictions, Windows 2003 Web is a
fantastic product.

--
You can get more with a kind word and a 2x4 than just a kind word.
 
L

Leythos

In article <vuldi3pb88vochj1dbm6qkavr7742jkkru@4ax.com>,
spam_narf_spam@crazyhat.net says...
> In message <MPG.218f71a02ed456c3989743@adfree.Usenet.com> Leythos
> <void@nowhere.lan> wrote:
>
> >> If you're talking internal LAN DNS, then you're quite correct.
> >>
> >> However, if you're talking about an internet facing web server, you need
> >> some sort of DNS service too. This is very often outsourced to your
> >> domain registrar, but there is no practical reason why you need to, if
> >> you have a reasonably skilled DNS admin kicking around and have needs
> >> that exceed your domain registrar's abilities, then it's a very common
> >> and very valid setup.
> >>
> >> As it turns out, Windows 2003 Web's DNS server is perfectly capable of
> >> handling this role.
> >
> >If you can only afford that cheap version of Windows, with limited CPU
> >support, then my guess is that you're not actually going to purchase a
> >quality firewall device, proper configuration, and you're going to cheap
> >out on other things. There is no reason to be running your own public
> >facing DNS on your Web server also - it's just another point of exposure
> >to be attacked.
> >
> >Yes, it "Can" be done, not it's not a best practice.
>
> Sure, that makes sense. I always spend as much money as possible when
> buying licensing to ensure that I get extra features I know I won't
> need. I like knowing I can install 16 CPUs, even if the hardware only
> has one socket, and having support for 8GB of RAM even though the
> intended application will run fine on 1GB-2GB of RAM, and that's all we
> intend to install.
>
> Is it a good solution for everyone? Obviously not. However, if you're
> only running a small to medium web server, and don't need to exceed the
> CPU, RAM, or other licensing restrictions, Windows 2003 Web is a
> fantastic product.

And that doesn't change the fact of what I typed.

Since you're asking about DNS, it makes one wonder what else you didn't
know or do following proper standards - that's all.

--

Leythos
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam999free@rrohio.com (remove 999 for proper email address)
 
D

DevilsPGD

In message <MPG.2190d35eeb84ea57989764@adfree.Usenet.com> Leythos
<void@nowhere.lan> wrote:

>Since you're asking about DNS, it makes one wonder what else you didn't
>know or do following proper standards - that's all.

1) I'm not asking about DNS.

2) The original poster isn't asking about DNS, they're asking about
whether the feature they need is included in a specific licensing
package. The documentation online isn't especially clear either
(especially since the answer is "maybe", depending on what features you
need)

--
You can get more with a kind word and a 2x4 than just a kind word.
 
You must log in or register to reply here.

Similar threads

C
SQL cluster object is not in DNS server and AD DC
Replies
0
Views
30
CYSan
C
G
SYSVOL on Domain Controllers do not Match
Replies
0
Views
28
Gyan Gearon
G
P
How to make exception on DNS Forwarder for a DNS entry
Replies
0
Views
50
Paul YK Chen
P
N
Why can’t i access public Wi-Fi login pages (DNS issues)?
Replies
0
Views
20
Nele Pallemaerts1
N
M
DNS over TLS (DoT) support for the DNS Server role
Replies
0
Views
41
Micah S. Harwell
M
Back
Top Bottom