The authoritative nameservers I've used recently all do the "right thing"
there: no RRs => NXDOMAIN.
FYI, BIND 9, which must be the most popular authoritative server on
the net, does what 4592 says, NOERROR at an empty nonterminal:
$ host -t txt foo.bar.sp.am light.lightlink.com
Using domain server:
Name: light.lightlink.com
Address: 64.57.176.2#53
Aliases:
foo.bar.sp.am descriptive text "Hi there"
[johnl(_at_)joyce ~]$ host -t txt bar.sp.am light.lightlink.com
Using domain server:
Name: light.lightlink.com
Address: 64.57.176.2#53
Aliases:
bar.sp.am has no TXT record
[johnl(_at_)joyce ~]$ host -t txt har.bar.sp.am light.lightlink.com
Using domain server:
Name: light.lightlink.com
Address: 64.57.176.2#53
Aliases:
Host har.bar.sp.am not found: 3(NXDOMAIN)
And the recursive servers I have handy also do the "right thing" and
don't synthesize fake answers.
No argument there, no cache synthesizes answers, even the ones that
have enough DNSSEC data to do so reliably.
For layering something on top of DNS the deployed implementation is
the only spec that matters - what's implemented trumps what would be
nice.
Well, for the third time, yeah.
With that said, I still like my b-tree hack, ...
If you're going to the effort of adding that much functionality
at the client end, switching to a better matched protocol instead
might be better. All the high traffic DNSBL users already use
a push protocol of sorts. Moving to a better, more standardized
one might be a win.
Huh? The functionality to the client is the same, it looks up an IP
address and finds out whether or not it's listed. The internal
representation is different, and it should cache a lot better. The
extra work at the client is actually quite small, a simple loop to
walk through some easily parsed records.
R's,
John
_______________________________________________
Asrg mailing list
Asrg(_at_)irtf(_dot_)org
http://www.irtf.org/mailman/listinfo/asrg