From owner-freebsd-net Wed Aug 8 21: 3:24 2001 Delivered-To: freebsd-net@freebsd.org Received: from ns1.austclear.com.au (ns1.austclear.com.au [192.43.185.68]) by hub.freebsd.org (Postfix) with ESMTP id 4C11837B401; Wed, 8 Aug 2001 21:03:18 -0700 (PDT) (envelope-from ahl@austclear.com.au) Received: from tungsten.austclear.com.au (tungsten.austclear.com.au [192.168.166.65]) by ns1.austclear.com.au (8.11.2/8.11.3) with ESMTP id f7943Gv15317; Thu, 9 Aug 2001 14:03:16 +1000 (EST) (envelope-from ahl@austclear.com.au) Received: from tungsten (tungsten [192.168.166.65]) by tungsten.austclear.com.au (8.9.3/8.9.3) with ESMTP id OAA03852; Thu, 9 Aug 2001 14:03:16 +1000 (EST) Message-Id: <200108090403.OAA03852@tungsten.austclear.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Hassan Halta Cc: freebsd-questions@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: DNS and nslookup problem In-Reply-To: Message from Hassan Halta of "Wed, 08 Aug 2001 21:54:11 EST." <20010808214918.R14553-100000@quark.cs.earlham.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Aug 2001 14:03:16 +1000 From: Tony Landells Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org hassan@cs.earlham.edu said: > Here's a problem, say I am using nslookup to look for ibm.net, but > when I do that, I will get ibm.net.cs.earlham.edu instead on ibm.net > by itself, or non existence domain...etc. At the beginning it seems to > be a missing period problem, but I assure you it's not. A friend of > mine fixed it temporarly if she adds nslookup -nosea , and everything > goes fine, but if someone is using us as a nameserver, that will not > help. I was wondering if there are some ways to solve or debug this > problem. Nslookup is a client, which really has little to do with your nameserver (apart from sending queries to it), so what you see with nslookup isn't necessarily what other people see. And nslookup actually uses a custom resolver library that isn't the same as would be used by "normal" clients. There are many tools, such as dig, which will give you a much better idea of what's going on. Tony -- Tony Landells Senior Network Engineer Ph: +61 3 9677 9319 Australian Clearing Services Pty Ltd Fax: +61 3 9677 9355 Level 4, Rialto North Tower 525 Collins Street Melbourne VIC 3000 Australia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message