DNS Serving form desktop

[Peter Gort]

Hi Bryann,

Oh how I wish it were that simple.

For work reasons (this is not optional I have to do this) I am  
running a Mac OS X Server as a development server in my little home/ 
office network.  There is no choice in the matter of DNS, it has to  
have it. Lots of services break if it doesn't have a DNS server  
separate from itself.  "A" & "PTR" records are compulsory, and MX  
record as well if I choose to run the mail server (which I sometimes  
need to do when testing something I've written).  The server has 3 IP  
interfaces, ethernet, wireless, and firewire.  Firewire networking  
performance in a small office has to be seen to be believed, whole CD  
images copy faster than I can get out to the kitchen and put the  
coffee pot on;-)

I take your point about installing server and adding KDE to it, that  
probably would have been simpler in the long run.  Might do that this  
evening or tomorrow.  For the moment I found a nice little utility  
that configures Bind in Mac OS X, so it's idling in OSX at the  
moment, with junior champing at the bit.....he really digs KDE and  
can play around in it for hours, just exploring.  And it's school  
holidays until the end of January <sigh>.

School work isn't a problem, he's a year or three away yet from  
writing assignments on the computer.  Besides, he can get time on the  
Powerbook if he can kick his mother and sister off it for long  
enough ;-)

Peter

On 02/01/2007, at 1:27 PM, bryann wrote:

> I have a hard time trying to figure why to bother with DNS on a home
> network. I have a WORK network/home use also /network all together 7
> machines plus router switch etc.
> The only nameserver use is internet on a local coop WLAN accessing the
> internet.
>
> Locally it is simpler to use a Hosts list.