From owner-freebsd-current  Sat Jun 15 19:22:20 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id TAA01674
          for current-outgoing; Sat, 15 Jun 1996 19:22:20 -0700 (PDT)
Received: from intercore.com (num1sun.intercore.com [199.181.243.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA01666
          for <current@freebsd.org>; Sat, 15 Jun 1996 19:22:13 -0700 (PDT)
Received: (robin@localhost) by intercore.com (8.7.1/8.6.4) id WAA02070; Sat, 15 Jun 1996 22:18:52 -0400 (EDT)
From: Robin Cutshaw <robin@intercore.com>
Message-Id: <199606160218.WAA02070@intercore.com>
Subject: Re: 2.2-960612-SNAP resolver problems
To: nate@sri.MT.net (Nate Williams)
Date: Sat, 15 Jun 1996 22:18:50 -0400 (EDT)
Cc: current@freebsd.org
In-Reply-To: <199606151626.KAA24720@rocky.sri.MT.net> from "Nate Williams" at Jun 15, 96 10:26:57 am
X-Mailer: ELM [version 2.4 PL21]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> What does nslookup do?
> 

It complains that it can't reverse resolve the nameserver's IP address
and exits.

I played with this for quite a while today.  I re-installed after making
a new boot image.  The NFS-based install failed when trying to resolve
the hostname to mount.  I then used an FTP install and it failed
trying to resolve the ftp host name.  After the NFS failed again,
I tried NFS back-to-back and it worked.  After booting, I got the
same name resolver problems.

So, more playing.  The box has a dec 21140 10/100 card running at 10
for the primary network interface.  It also has a dual 21040 card
for secondary networks.  I pulled the 21140 and made one of the
other interfaces the primary and noticed that is was enabled on
boot but when the "uha0" was probed (and not found), the interface
went down.  After removing the uha0 entry, I rebooted with the
original configuration and now everything works fine.

How the uha0 probe would affect only the dns lookups via the 21140
board is beyond me.


Well, it works now...

robin