From 4a76b6a7cdd9ab1b7030eadc65adcf5168a6b887 Mon Sep 17 00:00:00 2001
From: JP Mens <jp@mens.de>
Date: Mon, 12 Feb 2018 09:37:37 +0100
Subject: [PATCH] Change wording to indicate may not XFR instead of cannot

When a client has no permission to AXFR a zone from a server, the following diagnostics are logged:

```
AXFR of domain 'example' denied: client IP 10.0.0.1 has no permission
AXFR of domain 'example' failed: 10.0.0.1 cannot request AXFR
```

I feel the word _cannot_ is incorrect and should be _may not_ to indicate permission.
---
 pdns/tcpreceiver.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pdns/tcpreceiver.cc b/pdns/tcpreceiver.cc
index 3e4c00e596..49d2b30d87 100644
--- a/pdns/tcpreceiver.cc
+++ b/pdns/tcpreceiver.cc
@@ -585,7 +585,7 @@ int TCPNameserver::doAXFR(const DNSName &target, shared_ptr<DNSPacket> q, int ou
     }
 
     if (!canDoAXFR(q)) {
-      L<<Logger::Error<<"AXFR of domain '"<<target<<"' failed: "<<q->getRemote()<<" cannot request AXFR"<<endl;
+      L<<Logger::Error<<"AXFR of domain '"<<target<<"' failed: "<<q->getRemote()<<" may not request AXFR"<<endl;
       outpacket->setRcode(RCode::NotAuth);
       sendPacket(outpacket,outsock);
       return 0;
-- 
2.47.2