Re: [ngIRCd-ML] Problem with host resolving with ngircd

Hi Martin!

My irc-server ran perfect the last few weeks, but yesterday I upgraded my BIND to 9.3.0 and today morning I recognized, that hosts are no longer resolved. Its just eg. mh@193.149.36.81 ... I'm really stuck right now. Upgrading my dns was the only thing I have done (the last time). Resolving itsself works fine (dig, rbl-lookups ...). ngircd seems to be the only daemon, that can't resolve anymore ...

Strange.

ngIRCd uses the standard POSIX functions to resolve hostnames, so there should be no difference to other daemons and tools like ping, ftp, telnet, sshd etc. pp.

dig and nslookup don't use the system functions but query the given name server themself.

Can other daemons/tools do successful reverse(!) lookups?

Regards Alex