Another great tool for FreeBSD is djbdns.  It is a nameserver suite, that is
very easy to setup and is very secure.  The cache and nameserver components
are split unlike bind which elimiates many security problems such as
nameserver poisoning.  There is a lot of information on the web, just do a
google search on "freebsd djbdns", and you will find some walk throughs.  An
afternoon of tinkering with it will get you a fast, reliable (mines been
running nonstop for 2 months) ans secure DNS system.

The great thing i've found with freebsd is that you can implement your
infrastructure with much cheaper hardware allowing you to have a dedicated
mailserver, samba server,  and nameserver instead of pilinig two or more on
one machine. It takes patience and time to learn the OS and its software, so
dont rush into any decisions until you feel comforatable with administering
them in a corporate environment.  Good luck.

E Thornton

----- Original Message ----- 
From: "Dragoncrest" <[EMAIL PROTECTED]>
Sent: Friday, July 11, 2003 1:07 AM
Subject: name all the uses for samba

> Ok, I've gotta convince my boss to switch from windows 2000 to freebsd for
> all our internal needs.  So far I've half convinced him, but I've hit a
> snag.  I know that Samba can be used for a lot of things, and I'm trying
> tell him all the things that Samba will do, but I can't think of many.
> you guys name all the uses for samba?  I've already talked him into
> replacing our windows firewall, mail and other basic servers with freebsd,
> but we've still got a couple of domain servers to get rid of and I know
> that Samba can replace them as well.  Can you guys help me out here?
> toss in a little TCO jargon so that he sees it both from a technical side
> as well as what matters most ot him.  Money.  THanks!!
> _______________________________________________
> [EMAIL PROTECTED] mailing list
> To unsubscribe, send any mail to

[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to