From owner-freebsd-ports@FreeBSD.ORG Mon Mar 14 18:34:56 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C034A16A4CE for ; Mon, 14 Mar 2005 18:34:56 +0000 (GMT) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FA2A43D1F for ; Mon, 14 Mar 2005 18:34:56 +0000 (GMT) (envelope-from craig@yekse.gank.org) Received: by ion.gank.org (mail, from userid 1001) id 19DD32B724; Mon, 14 Mar 2005 12:34:56 -0600 (CST) Date: Mon, 14 Mar 2005 12:34:53 -0600 From: Craig Boston To: Jon Drews Message-ID: <20050314183452.GA13267@nowhere> Mail-Followup-To: Craig Boston , Jon Drews , FreeBSD Ports References: <8cb27cbf05031211126ca5f67d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8cb27cbf05031211126ca5f67d@mail.gmail.com> User-Agent: Mutt/1.4.2.1i cc: FreeBSD Ports Subject: Re: Why does Xfce 4.2 have to query a DNS ? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2005 18:34:56 -0000 On Sat, Mar 12, 2005 at 12:12:22PM -0700, Jon Drews wrote: > My question is why should a desktop have to check for a dns ? I may > have misidentified the problem. However I am curious as to why it > takes almost 2 minutes for the Xterm to open., when I am dialed out on > a modem. I don't know why xfce does this, but it's not the first time I've seen a similar problem. ISTR an old GNOME pager applet that would send out lots of DNS queries when mousing over it... As a workaround, you may want to consider adding an entry to your /etc/hosts file for the local machine. If your IP changes often (as it probably would on a modem connection), just put an entry for 127.0.0.1 with your hostname. That should prevent xfce or anything else from trying to contact an external DNS server when resolving the local hostname. I've only run into one piece of software that has problems with doing that -- Kerberos 5 seems to have trouble getting tickets for rlogin when the hostname doesn't resolve to its real (network) IP. Haven't had a problem with anything else. HTH, Craig