From owner-freebsd-questions@FreeBSD.ORG Mon Jan 24 10:15:12 2005 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 DBF9316A4CE for ; Mon, 24 Jan 2005 10:15:12 +0000 (GMT) Received: from grover.logicsquad.net (ppp38-159.lns1.adl1.internode.on.net [150.101.38.159]) by mx1.FreeBSD.org (Postfix) with SMTP id 95A3443D1F for ; Mon, 24 Jan 2005 10:15:10 +0000 (GMT) (envelope-from paulh@logicsquad.net) Received: (qmail 96074 invoked by uid 1000); 24 Jan 2005 10:15:09 -0000 Date: Mon, 24 Jan 2005 20:45:09 +1030 From: "Paul A. Hoadley" To: J65nko BSD Message-ID: <20050124101509.GC92421@grover.logicsquad.net> References: <20041216010258.GC93695@grover.logicsquad.net> <20041218224134.GA50538@grover.logicsquad.net> <41C5EB56.1000008@mac.com> <20041220122442.GA16576@grover.logicsquad.net> <20041223043908.GB27542@grover.logicsquad.net> <19861fba050120190671475bce@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="96YOpH+ONegL0A3E" Content-Disposition: inline In-Reply-To: <19861fba050120190671475bce@mail.gmail.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-questions@freebsd.org Subject: Re: Sendmail: host name lookup failure 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: Mon, 24 Jan 2005 10:15:13 -0000 --96YOpH+ONegL0A3E Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, Firstly, thanks for the comprehensive reply. On Fri, Jan 21, 2005 at 04:06:32AM +0100, J65nko BSD wrote: > It could be that the MS Windows DNS server, which is derived > from/patterned after named or however you want to call it, suffers > from a similar defect. Being not familiar with the MS DNS server, > you could find out whether it it possible to disable IPV6. BIND has > this option. Interesting. I did wonder whether disabling IPv6 in the Windows DNS server was possible---it was going to be something I looked at, but I stopped investigating once I found a workaround. > RE: resolving unqualified hostnames Thanks for the information and examples. > RE: .ns.chariot.net.au. and ns2.chariot.net.au. Thanks for the information. The problem I originally described, of course, is unrelated to these nameservers. I never made it quite clear enough in my original post, but the trouble I was having was with an internal view of our domain namespace. I'll let Chariot know their nameservers are broken. --=20 Paul. w http://logicsquad.net/ h http://paul.hoadley.name/ --96YOpH+ONegL0A3E Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFB9Mqs730Z/jysbzIRAowAAKCCa4svysMk4mbjtSPD2EkD9PNNAACdHAZt EOtsvaBh4ucJAPgukO7raQ0= =za/p -----END PGP SIGNATURE----- --96YOpH+ONegL0A3E--