When someone connects to nnrpd, nnrpd does a reverse lookup on the
clients IP address so it can look up the hostname in nnrpd.access.  If
the client's DNS information is incorrect, you will get this error.
Make sure your SOA record is correct, as well as your in-addr.arpa
data.

Derek <ddl@clipper.ssb.com> adds that another cause for this problem,
at least under SunOS 4.1.x, is that nnrpd wasn't linked with the proper
resolver library (statically or dynamically).  Even when you've
replaced Sun's fershlugger libresolv.a you've still gotta remind
yourself to _use_ it properly.


User Contributions:
Comment about this article, ask questions, or add new information about this topic:
Name:
E-mail:
Display email publicly
Security Code:
Comment:  (50-4000 characters)

 




Archived related questions and answers