From owner-freebsd-current@FreeBSD.ORG Wed Dec 17 14:45:28 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8347F16A4CE for ; Wed, 17 Dec 2003 14:45:28 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-234.dsl.lsan03.pacbell.net [63.207.60.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64F3B43D1D for ; Wed, 17 Dec 2003 14:45:27 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E7CC166C4F; Wed, 17 Dec 2003 14:45:26 -0800 (PST) Date: Wed, 17 Dec 2003 14:45:26 -0800 From: Kris Kennaway To: tn Message-ID: <20031217224526.GA41308@xor.obsecurity.org> References: <3FDCD835.4020004@giallarhorn.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GvXjxJ+pjyke8COw" Content-Disposition: inline In-Reply-To: <3FDCD835.4020004@giallarhorn.org> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: Default internet domain not working in 5.2 RC1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Dec 2003 22:45:28 -0000 --GvXjxJ+pjyke8COw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 14, 2003 at 04:37:57PM -0500, tn wrote: > I just reinstalled 5.2 RC1 from the cdrom, have since updated to a=20 > custom kernel. > The problem is that whenever i try to resolve any hosts in my domain=20 > without using a fully qualified domain name the look up fails. >=20 > Host name resolution works on all other machines within the network=20 > without a problem. > All machines have the following in /etc/resolv.conf: > domain giallarhorn.org > nameserver 192.168.1.1 > nameserver 192.168.1.5 >=20 > I even tried using the search keyword without any luck. Check for typos and other configuration differences between the machines. Failing that, obtain a tcpdump trace showing the DNS resolution attempts on the broken and working machines. Kris --GvXjxJ+pjyke8COw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/4NyGWry0BWjoQKURAiV/AJ4yuKfCfXIsGhb2RKsv/jfEfEaqpgCcCejj eHNE8ScgtONDWoVOYKDnzJU= =39oQ -----END PGP SIGNATURE----- --GvXjxJ+pjyke8COw--