Nothing to do with syslog-ng. It's the DNS, there should exist both the A -record and the PTR for the host. That is you should be able to resolve NAME-to-IP and also IP-to-NAME. -----Original Message----- From: syslog-ng-admin@lists.balabit.hu [mailto:syslog-ng-admin@lists.balabit.hu] On Behalf Of Asif Iqbal Sent: Friday, May 14, 2004 5:34 PM To: syslog-ng@lists.balabit.hu Subject: Re: [syslog-ng]cisco host not being resolved Badat, Qassim, ALABS wrote:

I resolved it, the problem was due to DNS and missing reverse entries for these hosts. Guess what, it was the logs in the syslog-ng that led to its own resolution !!!

Would you care to share the diff of the not working and working syslog.conf? I am having the same problem Thanks

_____

From: syslog-ng-admin@lists.balabit.hu [mailto:syslog-ng-admin@lists.balabit.hu] On Behalf Of Badat, Qassim, ALABS Sent: Friday, May 14, 2004 11:58 AM To: syslog-ng@lists.balabit.hu Subject: [syslog-ng]cisco host not being resolved

Hi,

I am new to syslog-ng so excuse my ignorance. I have installed syslog-ng 1.6.2 on Solaris 8. I am getting the logs but the host

names

are not being resolved. . Strangely logs from another vendor's does have the names resolved by syslog-ng. Any idea whats causing the problem for cisco ?

My syslog-ng.conf file:

options { long_hostnames(off); sync(0); };

source sys { sun-streams ("/dev/log" door("/etc/.syslog_door")); internal(); };

source net { udp(); };

destination network { file("/var/log/syslog-ng"); };

log { source(net); destination(network); };

log { source(sys); destination(network); };

Regards,

QB

-- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu There's no place like 127.0.0.1 _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html