mention dig +qr

diff --git a/pdns/recursordist/docs/appendices/FAQ.rst b/pdns/recursordist/docs/appendices/FAQ.rst
index b6ddbb3011c555c5200ba84dfb6229e613241136..8283cdf71ca0024272c412cbd3fe9c3993b5bfa9 100644 (file)
--- a/pdns/recursordist/docs/appendices/FAQ.rst
+++ b/pdns/recursordist/docs/appendices/FAQ.rst
@@ -37,7 +37,7 @@ But the example above is the Recursor responding to a client, and it is telling
 Or, to say it differently, the Recursor is telling the client that *questions* must fit in 512 bytes.
 This is fine for the Recursor - unlike an Authoritative, that might need to handle big UPDATE requests, the Recursor really only answers simple questions from clients, and those always comfortably fit in 512 bytes, because the maximum length of a DNS name is 256 bytes.
 
-Similarly, the maximum size of a response from the Recursor to a client is governed by the buffer size reported by the client, and the :ref:`setting-udp-truncation-threshold` setting in the Recursor configuration.
+Similarly, the maximum size of a response from the Recursor to a client is governed by the buffer size reported by the client (in ``dig``, you can see that number by doing ``dig +qr``), and the :ref:`setting-udp-truncation-threshold` setting in the Recursor configuration.
 
 To see the buffer size the Recursor is reporting to authoritatives, ask an authoritative::