From owner-freebsd-questions Fri Sep 29 12:44:31 2000 Delivered-To: freebsd-questions@freebsd.org Received: from bsdie.rwsystems.net (bsdie.rwsystems.net [209.197.223.2]) by hub.freebsd.org (Postfix) with ESMTP id B920737B650; Fri, 29 Sep 2000 12:44:27 -0700 (PDT) Received: from bsdie.rwsystems.net([209.197.223.2]) (1485 bytes) by bsdie.rwsystems.net via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Fri, 29 Sep 2000 14:38:05 -0500 (CDT) (Smail-3.2.0.111 2000-Feb-17 #1 built 2000-Jun-25) Date: Fri, 29 Sep 2000 14:38:04 -0500 (CDT) From: James Wyatt To: sthaug@nethelp.no Cc: jim@siteplus.net, jan@smartsoft.cc, freebsd-questions@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: DNS: having domain1.com and domain1.net point to the same IP. In-Reply-To: <31877.970245833@verdi.nethelp.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wow, reverse lookups only match some of the time?!?! I may be off-base again, but I thought a lot of things wanted reverse host entries that matched exactly for security verification. I read your last comment, but want to know what folks think would really happen. - Jy@ On Fri, 29 Sep 2000 sthaug@nethelp.no wrote: > > Reverse lookups are like Highlanders. "There can be only one." > > No. You can certainly have a reverse lookup returning multiple names. > Ie. the following is perfectly legal: > > $origin 3.2.1.in-addr.arpa. > 4 PTR name1.example.com. > 4 PTR name2.example.com. > 4 PTR name3.example.com. > > However, this does *not* necessarily mean that such a configuration > is good idea... > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message