Subject: pkg/12184: inn 2.3.1 nnrpd can't resolve host names
To: None <gnats-bugs@gnats.netbsd.org>
From: Wolfgang Rupprecht <wolfgang@wsrcc.com>
List: netbsd-bugs
Date: 02/11/2001 09:42:37
>Number:         12184
>Category:       pkg
>Synopsis:       inn 2.3.1 nnrpd can't resolve host names
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Feb 11 09:43:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Wolfgang Rupprecht
>Release:        NetBSD-current src: Feb 7, 2001 pkgsrc: Feb 10, 2001
>Organization:
W S Rupprecht Computer Consulting, Fremont CA
>Environment:
	
System: NetBSD capsicum.wsrcc.com 1.5R NetBSD 1.5R (WSRCC) #6: Wed Feb 7 21:08:07 PST 2001 wolfgang@capsicum.wsrcc.com:/v/src/netbsd/src/sys/arch/i386/compile/WSRCC i386
Architecture: i386
Machine: i386
>Description:
	
	inn 2.3.1 nnrpd can't resolve host names.  This is for a 
	machine that does have valid forward/reverse DNS entries
	(locally at least).

	$ host 192.83.197.1
	1.197.83.192.in-addr.arpa. domain name pointer capsicum.wsrcc.com.
	$ host capsicum.wsrcc.com
	capsicum.wsrcc.com. has address 192.83.197.1

	Observed on an x86 (little endian) with ipv6 compiled into
	kernel.  htonl() problem???  I'm having trouble gdbing the
	nnrpd code.  Attaching to the running process occurs too late
	to observe the resolver failure.
	
>How-To-Repeat:

	Read news, look at the news.info log file.

	Feb 10 14:54:47 capsicum nnrpd[7625]: ? cant gethostbyaddr 192.83.197.1 Resolver internal error -- using IP address for access


>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted: