From owner-freebsd-hackers Sat Aug 23 19:08:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA28873 for hackers-outgoing; Sat, 23 Aug 1997 19:08:07 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA28792 for ; Sat, 23 Aug 1997 19:07:55 -0700 (PDT) Received: from awfulhak.org (dev.lan.awfulhak.org [10.0.1.5]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id BAA26516 for ; Sun, 24 Aug 1997 01:19:31 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.7/8.8.6) with ESMTP id BAA00819 for ; Sun, 24 Aug 1997 01:19:30 +0100 (BST) Message-Id: <199708240019.BAA00819@awfulhak.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-hackers@freebsd.org Subject: Broken resolver/named Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 24 Aug 1997 01:19:30 +0100 From: Brian Somers Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a bit of a problem - that I can only put down to being the fault of either the resolver library or named. My /etc/resolv.conf says (in 2.2.2 & -current): domain lan.awfulhak.org (I have a local named running as a primary for ``lan.awfulhak.org'') If I try to resolve an unqualified name that doesn't exist (such as ``x''), the resolver sends two DNS queries (because the first fails). The first query is for ``x.lan.awfulhak.org'', and when that fails, it sends a query for ``x''. The resolver then says "Dunno who ``x'' is, I'll ask someone else.....". This is a bit of a dumb thing to do (I'm on a dial-up to real life)..... There is a compile-time option for named called "LOCALDOM" that allows you to say "domain lan.awfulhak.org" in named.boot, and have the second query answered with "dunno" immediately, but according to named, only broken resolvers send unqualified names to the DNS. Soooooo, does anyone know if the latest version of named deals with this, or if it just keeps the old philosophy of "your resolver is broken" ? BTW, I've tried using "search lan.awfulhak.org" in resolv.conf, and tried both combinations with a trailing ``.'' - makes no difference. IMHO, the resolver shouldn't be sending the second query. Should I look at fixing the resolver ? -- Brian , Don't _EVER_ lose your sense of humour....