From ab365f31ad706d69baa403ad8b568cffdb3794b7 Mon Sep 17 00:00:00 2001 From: Peter van Dijk Date: Thu, 15 Apr 2021 17:33:58 +0200 Subject: [PATCH] mention dig +qr --- pdns/recursordist/docs/appendices/FAQ.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pdns/recursordist/docs/appendices/FAQ.rst b/pdns/recursordist/docs/appendices/FAQ.rst index b6ddbb3011..8283cdf71c 100644 --- 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:: -- 2.47.2