From owner-freebsd-bugs  Wed Jan 14 16:41:41 1998
Return-Path: <owner-freebsd-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA22868
          for freebsd-bugs-outgoing; Wed, 14 Jan 1998 16:41:41 -0800 (PST)
          (envelope-from owner-freebsd-freebsd-bugs@FreeBSD.ORG)
Received: from kithrup.com (kithrup.com [205.179.156.40])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22852
          for <bugs@freebsd.org>; Wed, 14 Jan 1998 16:41:23 -0800 (PST)
          (envelope-from sef@kithrup.com)
Received: (from sef@localhost)
	by kithrup.com (8.8.8/8.8.7) id QAA28478
	for bugs@freebsd.org; Wed, 14 Jan 1998 16:41:19 -0800 (PST)
	(envelope-from sef)
Date: Wed, 14 Jan 1998 16:41:19 -0800 (PST)
From: Sean Eric Fagan <sef@kithrup.com>
Message-Id: <199801150041.QAA28478@kithrup.com>
To: bugs@FreeBSD.ORG
Subject: I tried to submit this via send-pr
Sender: owner-freebsd-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>Submitter-Id:   current-users
>Originator:     Sean Eric Fagan
>Organization:   Kithrup Enterprises, Ltd.
>Confidential:   no
>Synopsis:       "invalid hostname" is logged instead of IP address
>Severity:       serious
>Priority:       medium
>Category:       bin
>Release:        FreeBSD 2.2.5-STABLE i386
>Class:          sw-bug
>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: