In message 
<CAMm+Lwh=75oXwbubuB19rYhhMbfO=geapes_wes8xbyvdjn...@mail.gmail.com>, Phillip 
Hallam-Baker writes:
> On Sat, Oct 25, 2014 at 2:08 PM, Paul Vixie <p...@redbarn.org> wrote:
> 
> >
> >
> >   Stephane Bortzmeyer <bortzme...@nic.fr>
> >  Saturday, October 25, 2014 9:05 AM
> >
> > On Tue, Oct 21, 2014 at 02:14:49PM +0900,
> >  Masataka Ohta <mo...@necom830.hpcl.titech.ac.jp> 
> > <mo...@necom830.hpcl.titech.ac.jp> 
> wrote
> >  a message of 27 lines which said:
> >
> >
> >
> > Right, NXDOMAIN returned by some broken implementation to
> > empty non-terminals MUST NOT be interpreted that the
> > terminals does not exist.
> >
> >  i disagree with this. broken implementations who emit NXDOMAIN for empty
> > non-terminals cannot be used as an excuse not to develop and deploy correct
> > protocol and software enhancements. the internet has hundreds of years to
> > run yet, and these broken implementations are (a) shrinking not growing,
> > and (b) subject to rapid replacement when they start to encounter problems
> > with correct enhancements to their habitat.
> >
> 
> I agree with the sentiment. But there is a way to get the implementations
> to converge and that is to build something on top that consumes DNS
> Authoritative date and makes particular assumptions that is widely enough
> used to create an incentive.

People will learn.

There were nameservers that returned NXDOMAIN to AAAA queries.  These have
basically gone as they caused operational problems

There are nameservers that return NXDOMAIN to unknown EDNS options.  See
the bind-users archives.  These will go as people report them.

There are nameservers that return NXDOMAIN to empty non terminals.  These
too will go as soon as that start causing operational problems.  At the
moment NXDOMAIN and NODATA don't cause a issue for most applications.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: ma...@isc.org

_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to