Why do 3 out 5-10 POP clients get Unable to get canonical name of client, err = 0 Ok, one I should upgrade and likely will clear this problem, two it is not in the FAQ, as some POP clients do not get this message. Manually trying nslookup IP# fails. But works from remote computers. I've restarted (not just NOHUP) named twice. It started on March 19 for my POP attempts. It had been happening for one other client when they added a second computer to POP with. No changes to sendmail or popper had been made for at least 6 days (March 13). It comes down to perhaps someone doing an exploit? popper is in inetd.conf on FreeBSD. How would I try to clear this condition?
