From owner-freebsd-security Thu Nov 18 10:34:11 1999 Delivered-To: freebsd-security@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 31054154B2 for ; Thu, 18 Nov 1999 10:34:04 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA86668; Thu, 18 Nov 1999 10:33:55 -0800 (PST) (envelope-from dillon) Date: Thu, 18 Nov 1999 10:33:55 -0800 (PST) From: Matthew Dillon Message-Id: <199911181833.KAA86668@apollo.backplane.com> To: Matt Behrens Cc: David G Andersen , freebsd-security@FreeBSD.ORG, bsd@a.servers.aozilla.com, matt Subject: Re: [Systalk] localhost.org (fwd) References: Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org :: the IP alias resolve to domain.com both forward and reverse while the :: primary IP for the host resolves properly to host.domain.com both :: forward and reverse. : :Strictly speaking, this isn't a practical problem. Situations :where reverse and forward lookups must match (i.e. when using TCP :wrappers) operate by (a) having an IPv4 address (b) reverse-lookupping :it (c) forward-lookupping the result of the reverse lookup. If :you assign multiple A records to a single domain name, you are :breaking spec, but it doesn't cause any practical problems :(presently...) : :Matt Behrens :Owner/Administrator, zigg.com 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'. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message