<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>Hi Carsten,</div><div><br></div><div>Unfortunately, the issue is not limited to nslookup. Here's what I get when I run the same dig command you did below. Evidently something isn't right because my results should match yours. In a separate email, Chris asked if I was using this as a forwarder or resolver. I am using it as an authoritative, validating, recursive caching dns server as described here: <a href="https://calomel.org/unbound_dns.html">https://calomel.org/unbound_dns.html</a>. </div><div><br></div><div><div><b># dig 158.24.39.46.<a href="http://zen.spamhaus.org">zen.spamhaus.org</a>.</b></div><div><br></div><div>; <<>> DiG 9.9.4-rpz2.13269.14-P2 <<>> 158.24.39.46.<a href="http://zen.spamhaus.org">zen.spamhaus.org</a>.</div><div>;; global options: +cmd</div><div>;; Got answer:</div><div>;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 22741</div><div>;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1</div><div><br></div><div>;; OPT PSEUDOSECTION:</div><div>; EDNS: version: 0, flags:; udp: 4096</div><div>;; QUESTION SECTION:</div><div>;158.24.39.46.<a href="http://zen.spamhaus.org">zen.spamhaus.org</a>.<span class="Apple-tab-span" style="white-space:pre"> </span>IN<span class="Apple-tab-span" style="white-space:pre"> </span>A</div><div><br></div><div>;; AUTHORITY SECTION:</div><div><a href="http://zen.spamhaus.org">zen.spamhaus.org</a>.<span class="Apple-tab-span" style="white-space:pre"> </span>3546<span class="Apple-tab-span" style="white-space:pre"> </span>IN<span class="Apple-tab-span" style="white-space:pre"> </span>SOA<span class="Apple-tab-span" style="white-space:pre"> </span>need.to.know.only. <a href="http://hostmaster.spamhaus.org">hostmaster.spamhaus.org</a>. 1407271350 3600 600 432000 150</div><div><br></div><div>;; Query time: 39 msec</div><div>;; SERVER: 127.0.0.1#53(127.0.0.1)</div><div>;; WHEN: Sun Jul 27 15:52:37 CEST 2014</div><div>;; MSG SIZE rcvd: 122</div><div><br></div></div><br>
<br><div><div>On Jul 27, 2014, at 6:45 AM, Carsten Strotmann <<a href="mailto:unbound@strotmann.de">unbound@strotmann.de</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hello Patrick,<br><br>pcl-associates writes:<br><br><blockquote type="cite">Hi,<br><br>I don't know if I'm expecting too much from unbound but for certain<br>lookups I get a different result from unbound than I get from an<br>external DNS server. For example:<br></blockquote><br>Unbound is all good here, you're expecting too much from<br>"nslookup". Unbound returns the correct answers, but "nslookup" fails to<br>ask the wanted questions to Unbound (and does not show the DNS<br>queries). <br><br>Please try to use the tools "dig" or "drill" to send the query to<br>Unbound, the output will either give you a clue or, if posted here, will<br>give the participants of this mailing list an idea what might be wrong.<br><br>Example (using my local Unbound instance):<br><br>% dig 158.24.39.46.<a href="http://zen.spamhaus.org">zen.spamhaus.org</a>. <br><br>; <<>> DiG 9.10.0-P1 <<>> 158.24.39.46.<a href="http://zen.spamhaus.org">zen.spamhaus.org</a>.<br>;; global options: +cmd<br>;; Got answer:<br>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42320<br>;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1<br><br>;; OPT PSEUDOSECTION:<br>; EDNS: version: 0, flags:; udp: 4096<br>;; QUESTION SECTION:<br>;158.24.39.46.<a href="http://zen.spamhaus.org">zen.spamhaus.org</a>. IN A<br><br>;; ANSWER SECTION:<br>158.24.39.46.<a href="http://zen.spamhaus.org">zen.spamhaus.org</a>. 900 IN A 127.0.0.11<br>158.24.39.46.<a href="http://zen.spamhaus.org">zen.spamhaus.org</a>. 900 IN A 127.0.0.4<br><br>;; Query time: 205 msec<br>;; SERVER: 127.0.0.1#53(127.0.0.1)<br>;; WHEN: Sun Jul 27 15:43:37 CEST 2014<br>;; MSG SIZE rcvd: 90<br><br>-- <br>Carsten Strotmann<br>Email: <a href="mailto:cas@strotmann.de">cas@strotmann.de</a><br>Blog: <a href="http://strotmann.de">strotmann.de</a><br><br></blockquote></div><br></body></html>