You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems as if someone else also needs the unbound plugin for recursive DNS resolution for a mail server. I just built CoreDNS with the plugin, but it seems to work for me at the moment:
$ dig @localhost -p 8053 A 2.0.0.127.zen.spamhaus.org.; <<>> DiG 9.18.1-1ubuntu1-Ubuntu <<>> @localhost -p 8053 A 2.0.0.127.zen.spamhaus.org.; (1 server found);; global options: +cmd;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44429;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1;; OPT PSEUDOSECTION:; EDNS: version: 0, flags:; udp: 1232; COOKIE: 8cf772d423ce7983 (echoed);; QUESTION SECTION:;2.0.0.127.zen.spamhaus.org. IN A;; ANSWER SECTION:2.0.0.127.zen.spamhaus.org. 47 IN A 127.0.0.22.0.0.127.zen.spamhaus.org. 47 IN A 127.0.0.102.0.0.127.zen.spamhaus.org. 47 IN A 127.0.0.4;; Query time: 0 msec;; SERVER: 127.0.0.1#8053(localhost) (UDP);; WHEN: Fri May 13 19:42:08 CEST 2022;; MSG SIZE rcvd: 193
This issue can most likely be closed out since #28 was closed too. @chrisohaver Do we need a new release made with the updates done to miekg/unbound#18?
What happened:
When I try to resolve "2.0.0.127.zen.spamhaus.org." with dig:
dig a 2.0.0.127.zen.spamhaus.org.
I see CoreDNS outputs this:
[ERROR] Recovered from panic in server: "dns://:53" runtime error: index out of range [0] with length 0
So I added "debug" plugin and here is the result:
This is the Corefile I am using:
What you expected to happen:
It should not show the panic error.
But additionally, it should show an answer same as by using 1.1.1.1:
Instead it shows nothing (probably due to the crash), and sometimes I see this in the log:
[INFO] XXXXXXX:51176 - 61915 "A IN 2.0.0.127.zen.spamhaus.org. udp 67 false 4096" NXDOMAIN qr,rd,ra 136 0.755868575s
It is not able to resolve the DNSBL address?
How to reproduce it (as minimally and precisely as possible):
Use same Corefile as shown above and then use dig like this:
dig a 2.0.0.127.zen.spamhaus.org.
It should show the panic error, sometimes it shows the NXDOMAIN so just retry a few times.
Anything else we need to know?:
Environment:
Debian GNU/Linux 11 (bullseye)
CoreDNS-1.9.0
linux/amd64, go1.17.7
The text was updated successfully, but these errors were encountered: