Host Name Lookup Error
Folks, 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. 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. VJ Viraj Dixit 650-329-2118 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Host Name Lookup Error
On Feb 1, 2005, at 3:45 PM, Dixit, Viraj wrote: Folks, 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. 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. VJ Viraj Dixit 650-329-2118 IIRC, sendmail requires that the system `hostname' be a FQDN. Also, logs are kept under /var/log and not, /var/logs. HTH ___ Eric F Crist I am so smart, S.M.R.T! Secure Computing Networks -Homer J Simpson PGP.sig Description: This is a digitally signed message part
Re: Host Name Lookup Error
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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]