Technical article 110183

I see errors such as "popper: unable to get canonical name of client, err=XXX" in my syslog file.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5UnixWare 7.0.0UnixWare 7.0.1UnixWare 7.1.0

Written · Last revised

Problem

I see errors such as "popper: unable to get canonical name of
client, err=XXX" in my syslog file.  What does this mean and how
do I fix it?

Cause

Although the error code can vary slightly, the cause of the problem is generally the same:

Popper attempts to verify that the peer (client) IP address is
valid, logging a warning message when a connection is made with
a client whose IP address does not have a canonical name.  What
this means is that a gethostbyaddr(SLIB) lookup against a PTR
record (if using DNS) or /etc/hosts file returns either nothing
or something other than an official host name.
For systems using BSD 4.3 BIND (or later), popper also checks to
see if a canonical name lookup for the client returns the same
peer IP address, logging a warning message if it does not.  That
is, a reverse lookup is done against the A record (if using DNS)
or from /etc/hosts.

Solution

Changes to DNS or /etc/hosts should clear this problem up.  If
using /etc/hosts only, make sure all IPs in use on your network
have valid /etc/hosts entries, following the format:
IPaddr     nodename    fully-qualified-name    [aliases]
10.1.2.3   eeyore      eeyore.grump.com        www
Note that the aliases are optional.
If using DNS, make sure all IPs have correct A records, as well
as corresponding PTR records.  Make sure the node names are
spelled consistently and the proper use of "." is maintained.  If
in doubt, use nslookup(TC) to cross-check all client IPs.

See other articles in this database for proper DNS configuration.

See also

popper(ADM), gethostbyname(SLIB), gethostbyaddr(SLIB),
nslookup(TC)

ta107297, "How do I set up a primary nameserver and nameserver clients?"

ta107581, "How do I check DNS/named(ADMN) in.addr-arpa (reverse lookup) simply?"

"DNS & BIND," Albitz and Liu, O'Reilly and Associates.

From the Xinuos technical article database, record 110183. Reproduced with permission. The original is at www.sco.com/ta/110183, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.