   From: Dylan Penhale <dylanpenhale@(email surpressed)>
Subject: Re: Snow Leopard -- Fixes for Rush 102.42a9b and older
   Date: Fri, 25 Sep 2009 03:34:17 -0400

Msg# 1896
View Complete Thread (5 articles) | All Threads
Last Next

Yes I thought DNS at first but we thought we had it sorted as we whereusing the same settings as other non snow leopard machines. I assumeDNS is used to reverse lookup the IP addresses of the hostnames butthat this isn't cached anywhere.

It turns out that snow leopard treats .local in a different way toprevious apple operating systems, as far as I can tell. Usually thiswouldn't be a problem but as some of our domain uses .local thisappears to clash with the apple .local. which I believe is used forzeroconf type broadcast traffic.


Once we removed .local from the search suffix all is well again.

Thanks


On 25/09/2009, at 5:10 PM, Greg Ercolano wrote:

[posted to rush.general]

Dylan Penhale wrote:

We are experiencing slow performance issuing a rush -lah on snow
leopard.

Will the 102.42a9c maintenance release address this?


	I haven't seen a slowness problem on Snow Leopard
	with 'rush -lah'.

	Slowness with 'rush -lah' usually means hostname lookups
	aren't working correctly because it does a hostname<->IP
	lookup for each hostname in the rush/etc/hosts file, in
	order to show the IP addresses for each host.

	A very slow output of 'rush -lah' usually means the primary
	DNS server is being unresponsive.
	
	Check your DNS settings, to make sure the primary DNS server
	is responsive, and the search domain is set to your internal
	domain.

	Also; are there any hosts coming up with ???'s for IP's?
	If so, that's surely the cause, as it means DNS is failing
	the lookup for those hosts, and that can slow that report
	down quite a bit.

Last Next