Runing standalone DNS
 

I want to run a standalone DNS server in a small network separated from the i-net via a linux box. I've read that I need 'named' or 'bind' (what is the difference?). I've read on some docs that these servers are master-slave, i mean one main server and another one that connects to the first. Can I run only one server that serve the whole network? All I need from it is to connect seehere.myhost.net to 111.222.333.444 (only an example, ofcourse) if a browser request that. If it was only about my PC, I would write it in my /etc/hosts, but I can't do on all the network PCs.
So, what would happen if that server runs, and it is set as primary DNS on a machine.. this machine requests resolving of seethere.anotherhost.net which isn't at the database of the network NS. Would it search it in his master server database (unwillingly, I don't have another running 'master' server) or the requesting machine will refere to it's secondary DNS?
Thanks in advance : )

the application is called BIND (Berkeley Internet Name Daemon), but the server executable is called named (name daemon) you do not require an additional server at all, just check the bind-howto at tldp.org and that should take you through setting it up to server your network.

if you are only after a very basic system like you suggest, i'd recommend you to have a look at dnsmasq. this is a *VERY* simple dns server, which basically serves queries from a central /etc/hosts or relays to external mail servers. it's very nice, and requires absolutely minimal configuration.

dnsmasq should be more than enough in my case, but except from that task I really want to _learn_ something about the 'real way things go' ; ) so I'll try bind
thanks :)