<div>can u clarify what you mean by sound server. so basically what you are telling me if there is a windows dns server (active directory in server 2k3) mdns can replace the active directory server? also is there a way to curtail the network bottle necks?<br>
<br> </div>
<div><span class="gmail_quote">On 7/7/08, <b class="gmail_sendername">Ashley Pittman</b> <<a href="mailto:apittman@concurrent-thinking.com">apittman@concurrent-thinking.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Mon, 2008-07-07 at 15:59 +0200, Jon Aquilina wrote:<br>> is mdns strictly for the mac os or can it be incorporated into any<br>
> linux cluster??<br><br>It works under Linux, my sound server at home and the printers at work<br>use this quite satisfactorily.<br><br>I would caution against using it in a cluster however, it's design-goal<br>and benefit are to handle changing network environments where devices<br>
are being added to and removed from the network frequently. This is the<br>polar opposite of what you should try and aim for in a cluster where the<br>hardware configuration is known in advance and for the most part<br>constant. In addition it used to be the case there were performance<br>
issues associated with using zeroconf on large networks and the last<br>thing you want in a cluster is additional network traffic clogging up<br>the system.<br><br>Ashley Pittman.<br><br></blockquote></div><br><br clear="all">
<br>-- <br>Jonathan Aquilina