Running DNS 0n 2003 FIle Server

[snikde]

Hi,

I am setting up a home 2003 server (after running an NT PDC for years, I am retiring it)I am running Server 2003 Standard (not SBS 2003). I have opted not to run a domain anymore (not really worth it). So the server is configured as a file server and will be used in a peer-to-peer workgroup environment. Can I configure the server as a DNS server without running active directory? How would I set this up? I would like to be able to resolve machines by name vs. IP internally. Should I just use a hosts file. Network will be fairly static.

Thanks,
Guy

 

[adcfaq]

in ur home environemnt, u even don't need a wins or dns, 'coz broadcast will help u.

---------------------------------------
Sr. Directory Services/Exchange Consultant

http://adcfaq.8m.com/

 

[snikde]

Great!!! But what is broadcast and where can I find out more about it?

Nice web site too.

Guy

 

[ShackDaddy]

Snikde, you could go ahead and set up DNS. Don't worry about AD or anything. Just install the DNS service and create a forward lookup zone for your local "domain". Then create an A record for each user in your workgroup.

On each client system, you will want to have static addresses and you will want to set them to point at the DNS server for name resolution. You will also want to tell each client to append your DNS suffix (snikde.com or whatever your forwardlookupzone is called) by configuring that in the client DNS config page.

If you want your clients to have dynamic addresses, I'd use the DHCP server that comes with your server and have it dynamically populate your DNS zone. You have to set the zone to allow dynamic updates. It would be easier to do this than to set your clients up with static addresses.

For broadcast, you don't have to do anything. Every computer knows its own name and will respond when it hears a call for it.

For WINS, install WINS on the server and point the server at itself for WINS. Then point the clients at the server for WINS. Everything else is automagic.

As far as the best of these options, I haven't always had the best luck with broadcasts. When you try to ping a host that's offline, your pinging host will fail to resolve the name rather than not get a response. Having a centralized names -> IP mapping database makes things clearer. If all your systems are running XP, I'd go with the DNS solution. If you have a mix of older system, including Win98 and NT, I'd go with WINS. Wouldn't even hurt to do both WINS and DNS. WINS is dynamic, and if you set DNS/DHCP to be dynamic, then there's little management involved.

ShackDaddy

 

[snikde]

ShackDaddy,

Thanks for the tips! I currently have a router acting as the DHCP server but I think your idea of DNS and DHCP looks like it would be the best. I have read through various books and understand dynamic updates. No need for WINS as I run XP on all the clients.... well I have some Mac OS X boxes too.