From owner-freebsd-security Thu Nov 18 11:27:39 1999 Delivered-To: freebsd-security@freebsd.org Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (Postfix) with ESMTP id 5E1EA14D10 for ; Thu, 18 Nov 1999 11:27:25 -0800 (PST) (envelope-from matt@zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.9.3/8.9.3) with ESMTP id OAA21384; Thu, 18 Nov 1999 14:28:14 -0500 (EST) (envelope-from matt@zigg.com) Date: Thu, 18 Nov 1999 14:28:14 -0500 (EST) From: Matt Behrens To: Matthew Dillon Cc: David G Andersen , freebsd-security@FreeBSD.ORG, bsd@a.servers.aozilla.com, matt Subject: Re: [Systalk] localhost.org (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Today, Matt Behrens wrote: : Today, Matthew Dillon wrote: : : : I'm talking about CNAME records, not IN A records. : : : : BTW, assigning multiple A records to a single domain does not break spec : : at all. in A round robins entail other issues but none are related : : to the problem of 'domain.com' vs 'host.domain.com'. : : Sorry, I must have misunderstood. I caught the part about CNAMEs : but thought you were addressing A records in the second part. : : In any event, I thought I'd read somewhere that multiple A records : with the same IP violated spec. (It has been a few years since : I've read the RFCs; that was back when I was working on my now-defunct : Java resolver library.) Perhaps that was _formerly_ the case? And now upon closer inspection I discover that my original message was way off. Sorry about that. I meant to say that I thought it violated spec to have more than one domain name share the same _IP_ with A records, however in practical use it was not a problem. This solves the problem of having to multi-home a host just to give it two different domain names. Matt Behrens Owner/Administrator, zigg.com Chief Engineer, Nameless IRC Network To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message