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 262c12091cc50442f1355005d01d46f36b690876..c5f4f1095083877f3dda3cd66eed2ddc56b081c0 100644 (file)
--- a/pdns/rpzloader.cc
+++ b/pdns/rpzloader.cc
@@ -551,5 +551,8 @@ void RPZIXFRTracker(const std::vector<ComboAddress>& masters, boost::optional<DN
     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;
+    }
   }
 }