Re: Do I really need a DNS Server?
From: Herb Martin (news_at_LearnQuick.com)
Date: 12/21/04
- Next message: Herb Martin: "Re: DNS Forwarders - weird question"
- Previous message: Desmond Lee: "Re: Logon Server Unavailable"
- In reply to: Paul Medema: "Re: Do I really need a DNS Server?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 21 Dec 2004 15:05:55 -0600
"Paul Medema" <hydroteksystems@yahoo.com> wrote in message
news:#58SJw45EHA.1408@TK2MSFTNGP10.phx.gbl...
> Thanks.
> I will have a closer look at what you suggested.
> I think that right now I have it pointing to the ISP directly from the
> sever.
> My firewall handles the DHCP so I'll have to look into how that will work
as
> it assigns the DNS to the workstations.
If you cannot set the correct DNS server on the
Firewall then you must disable it's DHCP and
put DNS on your internal server instead.
It's free; it's easy; it's generally more customizable
than most cheap firewalls.
There is NOTHING wrong with having your
internal DNS servers forward to the Firewall,
firewall forward to the ISP -- in fact they are
usually very good reasons for this.
-- Herb Martin > > "Herb Martin" <news@LearnQuick.com> wrote in message > news:uGy0Wb84EHA.1596@tk2msftngp13.phx.gbl... > > "Paul Medema" <hydroteksystems@yahoo.com> wrote in message > > news:#S4L2774EHA.3756@TK2MSFTNGP14.phx.gbl... > >> OK, I feel very naive here... > >> I have a Windows 2003 Standard Edition Server. > >> I have a Symantec Firewall appliance that handles the DHCP and DNS. I > >> have > >> the firewall pointing to my ISPs DNS. > >> My question is do I need to have the windows 2003 server running a DNS > >> server as well? I'm fairly new to the Server management world and since > > this > >> is a small company I have not had much training so I'm flying a little > > blind > >> here... > > > > Yes, if you wish to resolve DNS names for internal > > machines you need a DNS server (that allows you to > > add address records.) > > > > If you wish to run a Win2000+ Active Directory you > > need that DNS to be dynamic. > > > > > >> Any suggestions about resources for me to pick up the basics of some of > > this > >> stuff? > > > > If you do not have an AD domain, and don't plan to add > > one then you MAY not need an internal DNS server, > > especially with only one Subnet, since broadcasts may > > resolve your machine names on a single segment but... > > > > Win2003 provides a DNS server, so since you own it the > > DNS server is free (i.e., already paid for). > > > > Open the DNS Management MMC (DNSMgmt.msc) and > > add the zone for your domain e.g., domain.local or > > domain.com (whatever you use locally or own publically). > > > > Add the zone (right click, it's that easy.) > > > > Make it dynamic IF you wish the machines to register > > automatically. > > > > On the forwarding tab, forward to your firewall appliance > > or directly to the ISP (I prefer the firewall and let it forward > > to the ISP.) > > > > Configure all clients to use ONLY the internal DNS server > > (not the firewall) unless you are unconcerned about > > internal resource name resolution. > > > > Servers are DNS clients too. > > > > For help use the built-in help and this search: > > > > [ DNS checklist ] > > > > > > -- > > Herb Martin > > > > > >> > >> Thanks > >> Paul > >> > >> > > > > > >
- Next message: Herb Martin: "Re: DNS Forwarders - weird question"
- Previous message: Desmond Lee: "Re: Logon Server Unavailable"
- In reply to: Paul Medema: "Re: Do I really need a DNS Server?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
