[64262] in North American Network Operators' Group

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

[OT] NXDOMAIN sanctified in RFC (Was: [Fwd: [IP] VeriSign to revive

daemon@ATHENA.MIT.EDU (Stephane Bortzmeyer)
Sat Oct 18 07:41:00 2003

From: Stephane Bortzmeyer <bortzmeyer@gitoyen.net>
To: Paul Vixie <vixie@vix.com>
Cc: nanog@merit.edu
In-reply-to: <g3u168n6bf.fsf@sa.vix.com> 
     (Paul Vixie <vixie@vix.com>'s message of 
     16 Oct 2003 22:52:52 -0000)
Date: Sat, 18 Oct 2003 13:35:33 +0200
Errors-To: owner-nanog-outgoing@merit.edu


On Thursday 16 October 2003, at 22 h 52, 
Paul Vixie <vixie@vix.com> wrote:

> i think i agree with where this was going, but it would be a fine thing if
> we all stop calling this NXDOMAIN.  the proper term is RCODE 3.  when you say
> NXDOMAIN you sound like you've only read the BIND sources and not the RFC's.
> NXDOMAIN is a BINDism, whereas RCODE 3 refers to the actual protocol element.

NXDOMAIN *was* a BINDism (you do not find it in RFC 1035) but it is now, not 
only a very common way to describe RCODE 3, but also a word you can find in 
RFC. Check 1536, 2136, 2308 and 2535.




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