From owner-freebsd-questions@FreeBSD.ORG Thu Jan 17 13:04:27 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 383AC3C1 for ; Thu, 17 Jan 2013 13:04:27 +0000 (UTC) (envelope-from bonomi@mail.r-bonomi.com) Received: from mail.r-bonomi.com (mx-out.r-bonomi.com [204.87.227.120]) by mx1.freebsd.org (Postfix) with ESMTP id E5413BF2 for ; Thu, 17 Jan 2013 13:04:26 +0000 (UTC) Received: (from bonomi@localhost) by mail.r-bonomi.com (8.14.4/rdb1) id r0HD7ksu066451; Thu, 17 Jan 2013 07:07:46 -0600 (CST) Date: Thu, 17 Jan 2013 07:07:46 -0600 (CST) From: Robert Bonomi Message-Id: <201301171307.r0HD7ksu066451@mail.r-bonomi.com> To: freebsd-questions@freebsd.org, tundra@tundraware.com Subject: Re: OT: What Might Break getbostbyname() ? In-Reply-To: <50F7783F.7020406@tundraware.com> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2013 13:04:27 -0000 > From owner-freebsd-questions@freebsd.org Wed Jan 16 22:08:13 2013 > Date: Wed, 16 Jan 2013 22:04:15 -0600 > From: Tim Daneliuk > To: FreeBSD Mailing List > Subject: OT: What Might Break getbostbyname() ? > > This is not really a FreeBSD problem ... in fact, it's happening on > a Solaris 10 machine. But because the TCP stack and its userland > interface came from BSD, I am hoping some kind soul might have > an insight into what's going on ... > > The machine in question does DNS lookups fine via dig or nslookup. > I believe these connect directly to the DNS server(s) specified > in /etc/resolv.conf. > > However, any program that uses gethostbyname() - like ping - fails > and says it cannot resolve the name. > > I'm looking for hints here on why or how gethostbyname() and/or > the network stack could get clobbered so as to not be able to talk > to the DNS servers which I know are reachable via dig and nslookup. dig and nslookup use THEIR OWN resolver routines, =not= the 'standard library' routines. Something that fouls the library routines will not affect dig and nslookup. Given this is Solaris, check /etc/nis.switch (may not be the exactly correct name, but close -- I haven't used Solaris in a decade). check both the file content, and permissions. You may have to run truss on ping to see what it's getting wrong.