From owner-freebsd-questions@FreeBSD.ORG Fri May 16 10:36:20 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2AD8037B401 for ; Fri, 16 May 2003 10:36:20 -0700 (PDT) Received: from mail.zoper.com (mail.zoper.com [198.78.65.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B75843F93 for ; Fri, 16 May 2003 10:36:19 -0700 (PDT) (envelope-from list@zettai.net) Received: (qmail 1015 invoked by uid 89); 16 May 2003 17:36:05 -0000 Received: from unknown (HELO ?63.74.27.90?) (list@zettai.net@63.74.27.90) by 0 with SMTP; 16 May 2003 17:36:05 -0000 User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.0.6 Date: Fri, 16 May 2003 13:36:13 -0400 From: george donnelly To: Roman Neuhauser , george donnelly Message-ID: In-Reply-To: <20030516092719.GZ1036@freepuppy.bellavista.cz> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit cc: FreeBSD Q's Subject: Re: dns resolution problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2003 17:36:20 -0000 [Roman Neuhauser wrote (neuhauser@bellavista.cz) on 5/16/03 5:27 AM] > # george@zettai.net / 2003-05-15 19:48:30 -0400: >> We recently made a IP changeover (we changed all IP's) and move to a VLAN >> config and now cronjobs, pings etc can not reolve hostnames. host and dig >> work fine. >> >> Does anyone have any idea why this could be? >> >> Running: >> >> FreeBSD 4.7 >> Djbdns, tinydns, dnscache >> dnscache runs on 127.0.0.1 >> >> resolv.conf looks like this: >> >> alpha# more /etc/resolv.conf >> domain alpha.zettai.net >> nameserver 127.0.0.1 >> nameserver 216.93.187.185 >> nameserver 216.93.178.185 >> nameserver 216.93.160.16 >> nameserver 216.93.170.17 >> >> 127.0.0.1 is dnscache, the resolver and cache > > ok. > >> the next two are ns1 and ns2, tinydns, authoritative > > this is quite probably (part of your) your problem. > >> the last 2 are the ISP's ns1 and ns2 > > not needed, remove them. thanks for your suggestion. i removed them but the problem persists. i also tried replacing resolv.conf with some values from another machine on the network where i'm not having this problem and this still does not solve it. <--> george donnelly - http://www.zettai.net/ - "We Love Newbies" :) Zope Hosting - Dynamic Website Design - Search Engine Promotion Yahoo, AIM: zettainet - MSN: zettainet@hotmail.com - ICQ: 51907738