From owner-freebsd-questions@FreeBSD.ORG Thu Jan 17 04:04:34 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 7EC88F1C for ; Thu, 17 Jan 2013 04:04:34 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) by mx1.freebsd.org (Postfix) with ESMTP id 49E4FCB9 for ; Thu, 17 Jan 2013 04:04:33 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.6/8.14.6) with ESMTP id r0H44GAZ078758 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 16 Jan 2013 22:04:16 -0600 (CST) (envelope-from tundra@tundraware.com) Message-ID: <50F7783F.7020406@tundraware.com> Date: Wed, 16 Jan 2013 22:04:15 -0600 From: Tim Daneliuk User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: FreeBSD Mailing List Subject: OT: What Might Break getbostbyname() ? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (ozzie.tundraware.com [192.168.0.1]); Wed, 16 Jan 2013 22:04:16 -0600 (CST) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: r0H44GAZ078758 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No 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 04:04:34 -0000 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. TIA, -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/