On Thu, Jun 16, 2011 at 1:43 PM, Gerald Drouillard <[email protected]> wrote: > On 6/16/2011 1:20 AM, Josh Patten wrote: >> DNS as a primary method for facilitating communication between >> endpoints, sipXecs servers, and gateways has proven to be an excellent >> method of enabling load balancing and, to a lesser extent, redundancy >> of sipXecs services. >> >> As it is currently implemented in sipXecs, DNS is the root cause of >> many outages and issues. This is because DNS configuration for proper >> sipXecs operation is complex for most network engineers/administrators >> and is very difficult for most telecom engineers to understand. This >> will only become more complex as future versions of sipXecs will add >> the capability for many more servers to be added to each sipXecs >> cluster, each possibly being deployed at a remote site to be used for >> survivability or load balancing. It has also been observed that >> individual sipXecs processes are making unnecessarily large amounts of >> DNS queries which can result in network congestion and extra load on >> the sipXecs cluster. > I agree about the excessive log writing. Maybe one could get that info > in debug mode. To reduce traffic then install a caching name server on > the sipx machine. >
Already on the plate : http://track.sipfoundry.org/browse/XX-9337, I'll take care of George _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
