Shouldn't these be logged to the rate-limit category and not to
query-errors?

Also, the ARM says:

          <title>The <command>query-errors</command> Category</title>
          <para>
            The <command>query-errors</command> category is
            specifically intended for debugging purposes: To identify
            why and how specific queries result in responses which
            indicate an error.
            Messages of this category are therefore only logged
            with <command>debug</command> levels.
          </para>

This seems to be incorrect, as these are obviously "info" level:

09-May-2014 02:17:22.690 query-errors: info: client 82.8.56.238#43456
(.): rate limit drop response to 82.8.56.0/24 for . IN ANY  (00000000)
09-May-2014 02:17:22.693 query-errors: info: client 1.1.1.1#48289 (.):
rate limit drop response to 1.1.1.0/24 for . IN ANY  (00000000)
09-May-2014 02:17:22.697 query-errors: info: client 1.1.1.1#31918 (.):
rate limit slip response to 1.1.1.0/24 for . IN ANY  (00000000)
09-May-2014 02:17:22.731 query-errors: info: client 1.1.1.1#38278 (.):
rate limit drop response to 1.1.1.0/24 for . IN ANY  (00000000)
09-May-2014 02:17:22.740 query-errors: info: client 1.1.1.1#9437 (.):
rate limit slip response to 1.1.1.0/24 for . IN ANY  (00000000)
09-May-2014 02:17:22.757 query-errors: info: client 1.1.1.1#65035 (.):
rate limit drop response to 1.1.1.0/24 for . IN ANY  (00000000)
09-May-2014 02:17:22.759 query-errors: info: client 64.180.193.23#20642
(.): rate limit drop response to 64.180.193.0/24 for . IN ANY  (00000000)
09-May-2014 02:17:22.761 query-errors: info: client 1.1.1.1#61409 (.):
rate limit slip response to 1.1.1.0/24 for . IN ANY  (00000000)
09-May-2014 02:17:22.765 query-errors: info: client 91.1.21.2#33868 (.):
rate limit drop response to 91.1.21.0/24 for . IN ANY  (00000000)
09-May-2014 02:17:22.778 query-errors: info: client 1.1.1.1#12664 (.):
rate limit drop response to 1.1.1.0/24 for . IN ANY  (00000000)
09-May-2014 02:17:22.784 query-errors: info: client 1.1.1.1#46721 (.):
rate limit slip response to 1.1.1.0/24 for . IN ANY  (00000000)
09-May-2014 02:17:22.811 query-errors: info: client 64.180.193.23#44319
(.): rate limit slip response to 64.180.193.0/24 for . IN ANY  (00000000)
09-May-2014 02:17:22.813 query-errors: info: client 82.8.56.238#24165
(.): rate limit slip response to 82.8.56.0/24 for . IN ANY  (00000000)
09-May-2014 02:17:22.816 query-errors: info: client 1.1.1.1#5450 (.):
rate limit drop response to 1.1.1.0/24 for . IN ANY  (00000000)
09-May-2014 02:17:22.837 query-errors: info: client 91.1.21.2#54501 (.):
rate limit slip response to 91.1.21.0/24 for . IN ANY  (00000000)
09-May-2014 02:17:22.846 query-errors: info: client 91.1.21.2#27096 (.):
rate limit drop response to 91.1.21.0/24 for . IN ANY  (00000000)
09-May-2014 02:17:22.851 query-errors: info: client 1.1.1.1#22952 (.):
rate limit slip response to 1.1.1.0/24 for . IN ANY  (00000000)
09-May-2014 02:17:22.876 query-errors: info: client 1.1.1.1#40638 (.):
rate limit drop response to 1.1.1.0/24 for . IN ANY  (00000000)
09-May-2014 02:17:22.894 query-errors: info: client 1.1.1.1#52580 (.):
rate limit slip response to 1.1.1.0/24 for . IN ANY  (00000000)
09-May-2014 02:17:22.914 query-errors: info: client 1.1.1.1#56138 (.):
rate limit drop response to 1.1.1.0/24 for . IN ANY  (00000000)