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