From c627111eeec6f80e5f66020c7613b4e408d2b193 Mon Sep 17 00:00:00 2001 From: "Jeremy C. Reed" Date: Thu, 18 Oct 2012 10:54:00 -0500 Subject: [PATCH] [master] add missing logger placeholder for RESOLVER_NON_IN_PACKET See ticket #2366 for details. Okayed by muks on jabber. Note that no test checked this and I don't introduce any test since I am pretty sure this code will no exist in any production version of a resolver (since won't limit IN only). --- src/bin/resolver/resolver_messages.mes | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/bin/resolver/resolver_messages.mes b/src/bin/resolver/resolver_messages.mes index 34a97ae49e..214519bd00 100644 --- a/src/bin/resolver/resolver_messages.mes +++ b/src/bin/resolver/resolver_messages.mes @@ -108,7 +108,7 @@ This error is issued when a resolver configuration update has specified a negative retry count: only zero or positive values are valid. The configuration update was abandoned and the parameters were not changed. -% RESOLVER_NON_IN_PACKET non-IN class request received, returning REFUSED message +% RESOLVER_NON_IN_PACKET non-IN class (%1) request received, returning REFUSED message This debug message is issued when resolver has received a DNS packet that was not IN (Internet) class. The resolver cannot handle such packets, so is returning a REFUSED response to the sender.