4 ms·
I notice you're using Googles DNS servers to do the lookups. This means it will "incorrectly" return NXDOMAINs for any spamhaus.org DNSBL lookup. For example:
by erbuhqergwer 17y ago
I notice you're using Googles DNS servers to do the lookups. This means it will "incorrectly" return NXDOMAINs for any spamhaus.org DNSBL lookup. For example:
http://dig.jsondns.org/IN/2.0.0.127.zen.spamhaus.org/A http://dig.jsondns.org/IN/2.0.0.127.zen.spamhaus.org/A
Yet doing the lookup using my own DNS server:
root@haven:~# host -t a 2.0.0.127.zen.spamhaus.org
2.0.0.127.zen.spamhaus.org A 127.0.0.2
2.0.0.127.zen.spamhaus.org A 127.0.0.4
2.0.0.127.zen.spamhaus.org A 127.0.0.10
root@haven:~#
- jf 17y agoInteresting. Do you have any suggestions for a better DNS server to use?
- erbuhqergwer 17y agoYou'll probably end up with the same issues with any publicly accessible recursive resolver. The only way to be sure you're getting "good" DNS responses is to use your own.
- jf 17y agoThe DNS library I'm using supports doing recursive queries - that'll likely be the next feature I'll add to dig.jsondns.