[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
identd and backresolving
Hi!
I'm facing very strange and annoying problem;
The identd (pidentd) refuses to backresolve addresses.
The point is that it worked some time before, I've done some changes in
configuration, I don't remember what exactly what, but since then it
ceased working.
It can backresolve from hosts but not bind, here's example from system
logs:
Feb 7 23:01:07 mapc identd[1069]: Connection from mapc.dyn.ml.org
Feb 7 23:01:24 mapc identd[1069]: from: 199.203.102.100 ( mapc.dyn.ml.org
) for: 3401, 113
This one has entry in /etc/hosts but via bind:
Feb 7 23:02:06 mapc identd[1076]: Connection from 132.68.7.4
Feb 7 23:02:07 mapc identd[1076]: from: 132.68.7.4 ( 132.68.7.4 ) for:
3826, 110
doesn't backresolve.
That DOESN'T have to do anything with the identd daemon itself, since it
worked before, and I even tried other version - same thing.
Here some files:
/etc/resolv.conf
nameserver 194.90.1.5
search netvision.net.il technion.ac.il
/etc/hosts
127.0.0.1 localhost localhost.localdomain
199.203.102.100 mapc.dyn.ml.org mapc.org.il mapc
/etc/host.conf
order hosts,bind
multi on
trim mapc.dyn.ml.org
hmm..that's all I can think about.
Note when using named (caching only) it was the same.
The pidentd sources:
ftp://ftp.cdrom.com/pub/FreeBSD/distfiles/pidentd-2.8.1.tar.gz
Please reply personally.
--Roman Shterenzon
========================================================================
Running Windows on a Pentium is like having a brand new Porsche but only
be able to drive backwards with the handbrake on.
(Unknown source)
========================================================================