rec: Log invalid RPZ content when obtained via IXFR

That kind of content was properly logged and handled when received
during the initial loading (AXFR) but not when received via an
incremental update.

(cherry picked from commit 55a99233728fc01e3946a97fb8dbb073a3003622)

diff --git a/pdns/rpzloader.cc b/pdns/rpzloader.cc
index fb88c8d675197ed4d0f2ef1b007bd71b6ac83591..4bf79e153205d61ece97adfc22b6971083624d66 100644 (file)
--- a/pdns/rpzloader.cc
+++ b/pdns/rpzloader.cc
@@ -587,5 +587,8 @@ void RPZIXFRTracker(const std::vector<ComboAddress>& primaries, const boost::opt
     catch (const std::exception& e) {
       g_log << Logger::Error << "Error while applying the update received over XFR for "<<zoneName<<", skipping the update: "<< e.what() <<endl;
     }
+    catch (const PDNSException& e) {
+      g_log << Logger::Error << "Error while applying the update received over XFR for "<<zoneName<<", skipping the update: "<< e.reason <<endl;
+    }
   }
 }