[30602] 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 (Valdis.Kletnieks@vt.edu)
Fri Aug 18 16:09:23 2000

Message-Id: <200008182006.e7IK6Oa33522@black-ice.cc.vt.edu>
To: "Gary E. Miller" <gem@rellim.com>
Cc: Joshua Goodall <joshua@roughtrade.net>, nanog@merit.edu
In-Reply-To: Your message of "Fri, 18 Aug 2000 12:33:01 PDT."
             <Pine.LNX.4.21.0008181228090.24973-100000@catbert.rellim.com> 
From: Valdis.Kletnieks@vt.edu
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1559947904P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 18 Aug 2000 16:06:24 -0400
Errors-To: owner-nanog-outgoing@merit.edu


--==_Exmh_-1559947904P
Content-Type: text/plain; charset=us-ascii

> RFC 1912, Sec 2.1:

Which is 'Informational', not standards track...

> " 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).

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

The major problem here is software packages that can't deal with the
possibility of setups like this:

www.mycorp.com  CNAME   round-robin.server.mycorp.com

round-robin.server.mycorp.com  A    198.168.1,1
			A 198.168.2.1
			A 198.168.3.1

Yes, major software vendors are still managing to get this Totally Wrong.

And when somebody at the VP level says something WILL be deployed in time
for another non-negotiable deadline (for instance, 25K students returning
to campus), you end up with some ugly ad-crockery with PTRs ;)

Yes, we'll fix the PTRs.  Soon as we get a patch from the vendor.  'Nuff
said. ;)

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



--==_Exmh_-1559947904P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.2 06/16/2000

iQA/AwUBOZ2XQHAt5Vm009ewEQKHFACdEUIcWgLl/kasuHAhvRlhgLZM438AniCO
xf96XVxF8ypFuyhYXPA/n8ew
=/w0q
-----END PGP SIGNATURE-----

--==_Exmh_-1559947904P--


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