3 Zář
2017
3 Zář
'17
2:16
Daniel,
I built from the code in git. git://git.nic.cz/knot-dns.git
Idon't know anything about recvmmsg. I'll look at the config summary.
When you tested this, did you use dig to send the query? When I use host
tosend the query, it appears to work, as host does not complain about
receiving a too-short reply. dig, on the other hand, seems to know it
is getting a message that is shorter thanthe expected header length. It
eventually claims that no server could be found, but it appears that it
is receiving something.
Maybe this recvmmsg setting will do the trick?No need to respond. I'll
be back in touch if I can't sort that out.
On 9/2/2017 2:38 AM, daniel.salzman(a)nic.cz wrote:
Hi Lisa,
Setting packet size to 0 and returning KNOTD_STATE_DONE is the proper way
how to inhibit a response. It also work in my simple test. Which version
of Knot do you have? Is recvmmsg utilized (see configure summary)?
Daniel
On 2017-09-01 19:45, Lisa Bahler wrote:
I've written aknot module, which is
functioning well. I've been asked
to add functionality to it that would inhibit any response from knot,
based upon the client's identity. I know the identity; I just need to
figure out how to inhibit a response.
I just noticed the rrl module, and I looked at what it does. I
emulated what I saw and set pkt->size = 0 and returned
KNOTD_STATE_DONE.
When I ran host -a, it returned that no servers could be reached.Â
When I ran dig ANY, I ultimately got the same response, but dig
complained three times about receiving a message that was too short in
length.
I really want NO message to be returned. How do I force this?
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users