[146158] in North American Network Operators' Group
Re: Performance Issues - PTR Records
daemon@ATHENA.MIT.EDU (Tom Lanyon)
Sun Nov 6 20:02:04 2011
From: Tom Lanyon <tom+nanog@oneshoeco.com>
In-Reply-To: <20111105024443.60D3DC18F5B@fafnir.remote.dragon.net>
Date: Mon, 7 Nov 2011 11:30:52 +1030
To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 05/11/2011, at 1:14 PM, Paul Ebersman wrote:
> tim> If PTR exists in zone file, serve it. Else, synthesize generic
> tim> reverse. Jobsagoodun.
>=20
> If all we're doing is lying with some generic answer that we hack our
> server to produce, why are we bothering?
Because some applications rely on it working (for some definition of =
"working").
> My contention is that (at least for end hosts), PTR records are mostly
> pointless and just overhead for DNS servers.
If you haven't set up PTR records for your end hosts, realistically =
you're going to be serving NXDOMAINs for them anyway, so there's not =
really any overhead introduced by supplying something generic instead...
Tom
