In message <[email protected]>, Paul Vixie writes: > > > Mark Andrews wrote: > > ... > > NXDOMAIN at a empty non terminal only came about as the result of > > bad wording in RFC 2535. "no names" should have been "no names > > with data" (the difference is crucial in determining which rcode > > is returned). Only RFC 2535 nameservers are allowed to return > > NXDOMAIN for a empty non-terminal and they should few and far between > > these days. Every other NXDOMAIN at a empty non terminal is the > > result of miss-interpreting STD 13 or a operational error e.g. > > missing delegation in a parent zone. > > i'd still like to see a standards track clarification. djb wrote a name > server which responds with nxdomain for empty nonterminals, and upon > re-reading the scriptures, i found that his interpretation wasn't > completely unreasonable.
Then please explain how RFC 1034 Section 4.3.2. Algorithm can return a Name Error for a empty non-terminal. I don't see it unless there is a missing delegation and that is a configuration error. I have zero problems with a cache returning Name Error if there is a configuration error. > -- > P Vixie -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [email protected] _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
