rec: Add comment about moving the aggressive NSEC cache check

diff --git a/pdns/syncres.cc b/pdns/syncres.cc
index 4170a1a2e7b6e110411b5f9b8ad04d547a2ecd8e..8e658c1d3d2778823110d6f62af2521dd4b9cc7e 100644 (file)
--- a/pdns/syncres.cc
+++ b/pdns/syncres.cc
@@ -1036,7 +1036,9 @@ int SyncRes::doResolveNoQNameMinimization(const DNSName &qname, const QType qtyp
 
   LOG(prefix<<qname<<": initial validation status for "<<qname<<" is "<<state<<endl);
 
-  #warning move aggressive NSEC check here? We know more about the zone and its status by now..
+  // XXX: We could move aggressive NSEC check here? We know more about the zone and its status by now,
+  // but on the other hand it means we have already done the zone cut determination which is not good
+  // Perhaps delay that change until after the DNSSEC zone cut refactoring?
 
   res = doResolveAt(nsset, subdomain, flawedNSSet, qname, qtype, ret, depth, beenthere, state, stopAtDelegation);