From sef@kithrup.com  Thu Jan 15 10:58:54 1998
Received: from kithrup.com (kithrup.com [205.179.156.40])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27813
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 15 Jan 1998 10:58:49 -0800 (PST)
          (envelope-from sef@kithrup.com)
Received: (from sef@localhost)
	by kithrup.com (8.8.8/8.8.7) id KAA05377;
	Thu, 15 Jan 1998 10:58:42 -0800 (PST)
	(envelope-from sef)
Message-Id: <199801151858.KAA05377@kithrup.com>
Date: Thu, 15 Jan 1998 10:58:42 -0800 (PST)
From: Sean Eric Fagan <sef@kithrup.com>
Reply-To: sef@kithrup.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: "invalid hostname" is logged instead of IP address
X-Send-Pr-Version: 3.2

>Number:         5500
>Category:       bin
>Synopsis:       "invalid hostname" is logged instead of IP address
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    brian
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jan 15 11:00:01 PST 1998
>Closed-Date:    Wed Mar 31 15:07:52 1999
>Last-Modified:  Wed Mar 31 15:09:12 PST 1999
>Originator:     Sean Eric Fagan
>Release:        FreeBSD 2.2.5-STABLE i386
>Organization:
Kithrup Enterprises, Ltd.
>Environment:

	
	FreeBSD 2.2.5-STABLE, on network.

>Description:

	
	If, during a network login, the remote host has an unsresolvable
	domain (e.g., its nameservers are unreachable and nslookup of
	the hostname returns "no such domain or host"), then "invalid
	hostname" is logged in utmp instead of the IP address.  This
	makes it impossible to tell where the login is from.

>How-To-Repeat:

	
	I'm not quite sure -- I don't know why I am getting an entire
	domain as invalid, but I've seen it happen a couple of times.
	Once is when I set up a PPP connection to work, in addition to my
	standard internet connection; this results in, I think, an
	inability to talk correctly to the nameserver for the domain.
	I've also seen it happen when the primary nameserver for a
	different domain was having network troubles, and was
	unroutable.


>Fix:
	
	
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: brian 
State-Changed-When: Wed Mar 31 14:00:33 PST 1999 
State-Changed-Why:  
Can the submitter retest with a more recent version of 
FreeBSD please. 


Responsible-Changed-From-To: freebsd-bugs->brian 
Responsible-Changed-By: brian 
Responsible-Changed-When: Wed Mar 31 14:00:33 PST 1999 
Responsible-Changed-Why:  
I'll close/fix this. 
State-Changed-From-To: feedback->closed 
State-Changed-By: brian 
State-Changed-When: Wed Mar 31 14:40:11 PST 1999 
State-Changed-Why:  
I tested on -stable and -current from March 25 by reconfiguring the 
interface on one machine to an unresolvable IP on the lan then rlogging 
onto the -stable and -current machines.  In both cases, both utmp and 
wtmp got the correct IP numbers.

State-Changed-From-To: closed->open
State-Changed-By: sef
State-Changed-When: Wed Mar 31 14:50:32 1999
State-Changed-Why:
Because that is *not* what I reported.  The most recent host I saw
demonstrate the problem was ppp-asfm02--080.sirius.net.  Doing an
nslookup of that reveals:

kithrup 1225% nslookup ppp-asfm02--080.sirius.net.
Server:  localhost
Address:  127.0.0.1

*** localhost can't find ppp-asfm02--080.sirius.net.: Non-existent host/domain

This is an entirely different situation from an "unresolvable IP".

State-Changed-From-To: open->closed
State-Changed-By: sef
State-Changed-When: Wed Mar 31 15:07:52 1999
State-Changed-Why:
Whether or not Brian did test what I needed, the later code does do what
I was just about to implement, although I need to check telnetd as well
as rlogind (having this same code in each is a bad idea).

>Unformatted:
