From owner-freebsd-bugs  Thu Jan 15 11:00:06 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA28043
          for freebsd-bugs-outgoing; Thu, 15 Jan 1998 11:00:06 -0800 (PST)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA28034;
          Thu, 15 Jan 1998 11:00:01 -0800 (PST)
          (envelope-from gnats)
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
X-Send-Pr-Version: 3.2
Subject: bin/5500: "invalid hostname" is logged instead of IP address
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         5500
>Category:       bin
>Synopsis:       "invalid hostname" is logged instead of IP address
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jan 15 11:00:01 PST 1998
>Last-Modified:
>Originator:     Sean Eric Fagan
>Organization:
Kithrup Enterprises, Ltd.
>Release:        FreeBSD 2.2.5-STABLE i386
>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:
	
	
>Audit-Trail:
>Unformatted: