[30598] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: lame delegations

daemon@ATHENA.MIT.EDU (Gary E. Miller)
Fri Aug 18 15:35:48 2000

Date: Fri, 18 Aug 2000 12:33:01 -0700 (PDT)
From: "Gary E. Miller" <gem@rellim.com>
To: Joshua Goodall <joshua@roughtrade.net>
Cc: nanog@merit.edu
In-Reply-To: <Pine.BSF.4.21.0008182109580.20704-100000@juice.shallow.net>
Message-ID: <Pine.LNX.4.21.0008181228090.24973-100000@catbert.rellim.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu


Yo Joshua!

On Fri, 18 Aug 2000, Joshua Goodall wrote:

> c) not everyone wants the reverse to match the forward (is this an RFC
>    violation? I hope not :)).

RFC 1912, Sec 2.1:

" Make sure your PTR and A records match.  For every IP address, there
   should be a matching PTR record in the in-addr.arpa domain.  If a
   host is multi-homed, (more than one IP address) make sure that all IP
   addresses have a corresponding PTR record (not just the first one).
   Failure to have matching PTR and A records can cause loss of Internet
   services similar to not being registered in the DNS at all.  Also,
   PTR records must point back to a valid A record, not a alias defined
   by a CNAME.  It is highly recommended that you use some software
   which automates this checking, or generate your DNS data from a
   database which automatically creates consistent data."

I have yet to hear a convincing argument why this RFC should be
ignored.  I have seen many problems when this is ignored.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 20340 Empire Ave, Suite E-3, Bend, OR 97701
	gem@rellim.com  Tel:+1(541)382-8588 Fax: +1(541)382-8676




home help back first fref pref prev next nref lref last post