From owner-freebsd-questions@FreeBSD.ORG Tue Feb 1 21:59:51 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2F8116A4CE for ; Tue, 1 Feb 2005 21:59:51 +0000 (GMT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEB5243D53 for ; Tue, 1 Feb 2005 21:59:51 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (8.12.6/MantshX 2.0) with ESMTP id j11Lxp7a001755; Tue, 1 Feb 2005 13:59:51 -0800 (PST) Received: from [10.1.1.245] (nfw2.codefab.com [199.103.21.225] (may be forged)) (authenticated bits=0)j11LxnOB000196; Tue, 1 Feb 2005 13:59:50 -0800 (PST) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <4642ace216ab7301ec6e8864d53ab252@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Tue, 1 Feb 2005 16:59:48 -0500 To: "Dixit, Viraj" X-Mailer: Apple Mail (2.619.2) cc: freebsd-questions@freebsd.org Subject: Re: Host Name Lookup Error X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Feb 2005 21:59:52 -0000 On Feb 1, 2005, at 4:45 PM, Dixit, Viraj wrote: > Just installed FreeBSD 5.3, all seems to be working except the error > from sendmail. I can ping the mail server in the domain that I am > trying to send the mail. But the mail gets send to my " > /var/spool/mqueue" directory. The error is "host name lookup failure". Configure /etc/resolv.conf with working nameservers, and then flush the queue of stuck mail. > I want to put this system on line as production system soon. On last > thing "syslogd" does not put out any logs under "var/logs". Any ideas, > I have been looking in FreeBSD archives. I would try restarting syslogd using the -d flag and use "logger -p kern.warn" to test it. Perhaps your /etc/syslog.conf file is not formatted correctly. Oh, you might need to touch any new logfiles you want to log to, if they do not already exist. -- -Chuck