From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 7 15:42:03 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C002D16A4CE for ; Tue, 7 Dec 2004 15:42:03 +0000 (GMT) Received: from mailfe01.swip.net (mailfe01.swip.net [212.247.154.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98C2D43D5C for ; Tue, 7 Dec 2004 15:42:02 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: Y1QAsIk9O44SO+J/q9KNyQ== Received: from [193.217.204.139] (HELO curly.tele2.no) by mailfe01.swip.net (CommuniGate Pro SMTP 4.2.6) with ESMTP id 233871404; Tue, 07 Dec 2004 16:42:00 +0100 Received: (from root@localhost) by curly.tele2.no (8.12.5/8.12.3) id iB7Fm1QW000470; Tue, 7 Dec 2004 16:48:01 +0100 (CET) (envelope-from hselasky@c2i.net) Date: Tue, 7 Dec 2004 16:47:59 +0100 From: Hans Petter Selasky To: David Malone Message-ID: <20041207164759.A283@curly.tele2.no> References: <20041206195709.A332@curly.tele2.no> <20041207093709.GA41269@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20041207093709.GA41269@walton.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Tue, Dec 07, 2004 at 09:37:09AM +0000 cc: freebsd-hackers@freebsd.org Subject: Re: hostname lookup problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 15:42:03 -0000 On Tue, Dec 07, 2004 at 09:37:09AM +0000, David Malone wrote: > On Mon, Dec 06, 2004 at 07:57:09PM +0100, Hans Petter Selasky wrote: > > I have come across a problem where res_send() goes into a minute-long wait > > loop, waiting for the hostname to be looked up, after a getaddrinfo() call. I > > have captured the packets sent/received, and according to the code the > > query response does not match. Is this a bug in libc or is it a DNS server > > problem? > > It looks like the recursive name server is doing something weird. The nameservers I use are 193.216.1.10 (primary DNS) (nic.daxnet.no) and 193.216.69.10 (secondary DNS) (ns.tele2.no) Output from "dig aaaa www.google.com @193.216.1.10": ; <<>> DiG 8.3 <<>> aaaa www.google.com @193.216.1.10 ; (1 server found) ;; res options: init recurs defnam dnsrch ;; wrong query name: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUERY SECTION: ;; www.google.akadns.net, type = AAAA, class = IN ;; wrong query name: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUERY SECTION: ;; www.google.akadns.net, type = AAAA, class = IN ;; res_nsend to server 193.216.1.10 193.216.1.10: Operation timed out Output from "dig a www.google.com @193.216.1.10": ; <<>> DiG 8.3 <<>> a www.google.com @193.216.1.10 ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 13, ADDITIONAL: 12 ;; QUERY SECTION: ;; www.google.com, type = A, class = IN ;; ANSWER SECTION: www.google.com. 3m22s IN CNAME www.google.akadns.net. www.google.akadns.net. 2m25s IN A 66.102.9.104 www.google.akadns.net. 2m25s IN A 66.102.9.99 ;; AUTHORITY SECTION: . 3d19h35m36s IN NS A.ROOT-SERVERS.net. . 3d19h35m36s IN NS H.ROOT-SERVERS.net. . 3d19h35m36s IN NS C.ROOT-SERVERS.net. . 3d19h35m36s IN NS G.ROOT-SERVERS.net. . 3d19h35m36s IN NS F.ROOT-SERVERS.net. . 3d19h35m36s IN NS B.ROOT-SERVERS.net. . 3d19h35m36s IN NS J.ROOT-SERVERS.net. . 3d19h35m36s IN NS K.ROOT-SERVERS.net. . 3d19h35m36s IN NS L.ROOT-SERVERS.net. . 3d19h35m36s IN NS M.ROOT-SERVERS.net. . 3d19h35m36s IN NS I.ROOT-SERVERS.net. . 3d19h35m36s IN NS E.ROOT-SERVERS.net. . 3d19h35m36s IN NS D.ROOT-SERVERS.net. ;; ADDITIONAL SECTION: A.ROOT-SERVERS.net. 19h40m39s IN A 198.41.0.4 H.ROOT-SERVERS.net. 19h40m39s IN A 128.63.2.53 C.ROOT-SERVERS.net. 19h40m39s IN A 192.33.4.12 G.ROOT-SERVERS.net. 19h40m39s IN A 192.112.36.4 F.ROOT-SERVERS.net. 19h40m39s IN A 192.5.5.241 B.ROOT-SERVERS.net. 19h40m39s IN A 192.228.79.201 J.ROOT-SERVERS.net. 19h38m52s IN A 192.58.128.30 K.ROOT-SERVERS.net. 19h38m52s IN A 193.0.14.129 L.ROOT-SERVERS.net. 19h38m52s IN A 198.32.64.12 M.ROOT-SERVERS.net. 19h38m52s IN A 202.12.27.33 I.ROOT-SERVERS.net. 19h38m52s IN A 192.36.148.17 E.ROOT-SERVERS.net. 19h40m39s IN A 192.203.230.10 ;; Total query time: 210 msec ;; FROM: curly.tele2.no to SERVER: 193.216.1.10 193.216.1.10 ;; WHEN: Tue Dec 7 16:27:56 2004 ;; MSG SIZE sent: 32 rcvd: 499 > > Do you know what is acting as your recursive DNS server? No. Yours -HPS