From owner-freebsd-bugs@FreeBSD.ORG Tue Jul 15 10:17:53 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 702EB37B401; Tue, 15 Jul 2003 10:17:53 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B78A43F3F; Tue, 15 Jul 2003 10:17:53 -0700 (PDT) (envelope-from dwmalone@FreeBSD.org) Received: from freefall.freebsd.org (dwmalone@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6FHHqUp081026; Tue, 15 Jul 2003 10:17:52 -0700 (PDT) (envelope-from dwmalone@freefall.freebsd.org) Received: (from dwmalone@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6FHHqXi081022; Tue, 15 Jul 2003 10:17:52 -0700 (PDT) Date: Tue, 15 Jul 2003 10:17:52 -0700 (PDT) From: David Malone Message-Id: <200307151717.h6FHHqXi081022@freefall.freebsd.org> To: bpatin@padecs.riss.net, dwmalone@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/44570: ftp behind VPN server fails host name lookup X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 17:17:53 -0000 Synopsis: ftp behind VPN server fails host name lookup State-Changed-From-To: feedback->closed State-Changed-By: dwmalone State-Changed-When: Tue Jul 15 10:12:45 PDT 2003 State-Changed-Why: This seems to be a bug in the name servers at the other end. ftp.perl.org is an alias for ftp.cpan.ddns.develooper.com. The DNS servers for that domain seem to be 142.132.1.82, 193.111.120.45 and 64.70.54.97. The first of these doesn't respond. The other two claim that the domain ftp.cpan.ddns.develooper.com doesn't exist if you ask them for a AAAA record, but claims it does exist if you ask it for an A record. Your local name server is caching the "doesn't exist" response from the AAAA record. You need to ask the people who run these name servers to fix them so it returns 0 records when asked for a AAAA record, rather than "no such domain". (See the dig commands below for the wrong and right responses...) David. % dig AAAA ftp.cpan.ddns.develooper.com @193.111.120.45 | fgrep status ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24551 % dig A ftp.cpan.ddns.develooper.com @193.111.120.45 | fgrep status ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61084 % dig AAAA ftp.cpan.ddns.develooper.com @64.70.54.97 | fgrep status ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62794 % dig A ftp.cpan.ddns.develooper.com @64.70.54.97 | fgrep status ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58525 % dig AAAA freefall.freebsd.org @216.136.204.126 | fgrep status ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54053 http://www.freebsd.org/cgi/query-pr.cgi?pr=44570