From: Greg Ercolano <erco@(email surpressed)>
Subject: Re: Snow Leopard -- Fixes for Rush 102.42a9b and older
   Date: Fri, 25 Sep 2009 05:03:45 -0400
Msg# 1897
View Complete Thread (5 articles) | All Threads
Last Next
> Once we removed .local from the search suffix all is well again.

	Sounds like you fixed it.

	Yes, I recommend avoiding the .local domain name suffix
	because that enables all that ZeroConf/Bonjours broadcast-based
	discovery stuff, including multicast DNS, which creates unreliable
	behavior that messes up network stability. ie:
	http://en.wikipedia.org/wiki/Zeroconf

	If you need zeroconf based stuff on your machines also running rush,
	you may be able to specify it without causing trouble IF you specify
	your internal domain first, and then .local after it. This way (maybe)
	regular DNS will be interrogated first, and then falls back to Bonjours
	only if that fails.

Dylan Penhale wrote:
> Yes I thought DNS at first but we thought we had it sorted as we where  
> using the same settings as other non snow leopard machines. I assume  
> DNS is used to reverse lookup the IP addresses of the hostnames but  
> that this isn't cached anywhere.

	Both OSX and Windows traditionally have DNS caching turned on
	as a default.

	"lookupd' used to be responsible for hostname caching in OSX,
	but now I think it's DirectoryServices(8) since lookupd was dropped.

	According to the docs, dscacheutil can be used to display the
	DNS cache (supposedly), ie. as root:

		dscacheutil -cachedump -entries Host

	However, when I do this on my snow leopard box, I get zippo.
	Even after I do things that /should/ trigger DNS cache hits,
	like pinging hosts by name, or running 'rush -lah'.

	Because of this empty output, I'm not entirely sure it IS
	caching namelookups by default in Snow Leopard. Just a casual
	observation though.. I haven't dug into SL deeply yet.

> It turns out that snow leopard treats .local in a different way to  
> previous apple operating systems, as far as I can tell.

	The bad behavior with .local has always been in there,
	it just creeps in whenever you start with a fresh machine,
	and forget to configure all the DNS stuff statically.

	When Bonjours creeps in, you can get flakey name lookups due
	to the broadcast based discovery stuff. I refer to this
	in the prerequisite docs as something to avoid:
	http://www.seriss.com/rush-current/rush/rush-admin-faq.html#ADMINFAQ-PREREQ

	(Search for hostname.local in that text)

> Usually this  
> wouldn't be a problem but as some of our domain uses .local this  
> appears to clash with the apple .local. which I believe is used for  
> zeroconf type broadcast traffic.

	Yes, correct.


	
-- 
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)

Last Next