From owner-freebsd-questions Thu Jan 25 7:48:58 2001 Delivered-To: freebsd-questions@freebsd.org Received: from femail10.sdc1.sfba.home.com (femail10.sdc1.sfba.home.com [24.0.95.106]) by hub.freebsd.org (Postfix) with ESMTP id 32BC437B6A5 for ; Thu, 25 Jan 2001 07:48:41 -0800 (PST) Received: from [192.0.0.27] ([24.7.223.67]) by femail10.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010125154840.JJVB6975.femail10.sdc1.sfba.home.com@[192.0.0.27]> for ; Thu, 25 Jan 2001 07:48:40 -0800 Mime-Version: 1.0 X-Sender: ralph99@mail.voicenet.com Message-Id: In-Reply-To: References: Date: Thu, 25 Jan 2001 10:48:39 -0500 To: freebsd-questions@freebsd.org From: Ralph Dratman Subject: Re: inetd services very slow to respond Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris, As you suggested, I did a query from the console of the slow server for resolution of the address of the client machine which was requesting services. Well, as it happens, the client machine I've been testing with does not have a DNS name, so I just put in >host 192.0.0.27 which happens to be the behind-the-firewall fake IP address of the requestor. And I got back "Host not found" with no delay. However, I've also experienced this delay from another machine, off-site, which DOES have a DNS name. I put in that name and after about a 5 second delay got back a numeric IP from the reverse lookup. If I put in the name, I get the IP. Again, without much delay. As I mentioned, the name daemon is running on the server that shows the slowdown. But DNS queries are not slow... of course they don't go through inetd, either. I don't see why this problem should be related to DNS. Note also (as described below) that the delay goes away when I run inetd with logging and debugging flags. Ralph ==================== >DNS resolution is of the IP address you are coming _from_..try doing >DNS queries for that IP address. > >Kris ======================= >Y'all, > >(AGAIN...) > >The name resolution is fast in both directions, whether to or from >the slow machine. There's no apparent delay. > >Here's another twist to the story: I stopped inetd and started it >again with -dl (debugging and logging to standard output) flags. Now >the services are operating without delay! > >C'mon, group, this is a QUESTION... > >(Did activity on this list suddenly go away or is that just my >imagination? I just joined the list, then received about 75 posts >from Tuesday and only ONE, so far, from Wednesday, and it's almost >the end of the day.) > >Ralph Dratman > >P.S. OOPS! I just re-read my original post and here's a correction: >I'm running FreeBSD 3.3, not 2.2 as I incorrectly stated in that >message. > >============== >>Sounds like DNS problems. What happens if you execute the following on >>the slow machine, >> >> % host >> >>Where the IP address or hostname is that of a machine that you connect >>from. > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message