FROM SNMPv2-CONF;
rec MODULE-IDENTITY
+<<<<<<< HEAD
LAST-UPDATED "202505270000Z"
+=======
+ LAST-UPDATED "202504290000Z"
+>>>>>>> 86b0c8c41 (Typos in comments and docs from Miod)
ORGANIZATION "PowerDNS BV"
CONTACT-INFO "support@powerdns.com"
DESCRIPTION
"This MIB module describes information gathered through PowerDNS Recursor."
+<<<<<<< HEAD
REVISION "202505270000Z"
DESCRIPTION "Added metric for missing ECS in reply"
+=======
+ REVISION "202504290000Z"
+ DESCRIPTION "Added metrics related to cookies"
+>>>>>>> 86b0c8c41 (Typos in comments and docs from Miod)
REVISION "202408280000Z"
DESCRIPTION "Added metric for too many incoming TCP connections"
FROM SNMPv2-CONF;
rec MODULE-IDENTITY
+<<<<<<< HEAD
LAST-UPDATED "202505270000Z"
+=======
+ LAST-UPDATED "202504290000Z"
+>>>>>>> 86b0c8c41 (Typos in comments and docs from Miod)
ORGANIZATION "PowerDNS BV"
CONTACT-INFO "support@powerdns.com"
DESCRIPTION
"This MIB module describes information gathered through PowerDNS Recursor."
+<<<<<<< HEAD
REVISION "202505270000Z"
DESCRIPTION "Added metric for missing ECS in reply"
+=======
+ REVISION "202504290000Z"
+ DESCRIPTION "Added metrics related to cookies"
+>>>>>>> 86b0c8c41 (Typos in comments and docs from Miod)
REVISION "202408280000Z"
DESCRIPTION "Added metric for too many incoming TCP connections"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
- "Matching cookies recieved"
+ "Matching cookies received"
::= { stats 155 }
cookieMismatchTcp OBJECT-TYPE
MAX-ACCESS read-only
STATUS current
DESCRIPTION
- "Authoritative serve sent a reply bnack without cookie"
+ "Authoritative server sent a reply back without cookie"
::= { stats 158 }
cookieRetry OBJECT-TYPE
New Settings
^^^^^^^^^^^^
-- The :ref:`setting-yaml-outgoing.cookies` settings has been introduced to implement cookie support for contacting authoritative servers and forwarders. See :rfc:`7873` and :rfc:`9018`.
+- The :ref:`setting-yaml-outgoing.cookies` setting has been introduced to implement cookie support for contacting authoritative servers and forwarders. See :rfc:`7873` and :rfc:`9018`.
:program:`rec_control`
^^^^^^^^^^^^^^^^^^^^^^
{
'name': 'cookie-matched',
'lambda': '[] { return g_Counters.sum(rec::Counter::cookieMatched); }',
- 'desc': 'Matching cookies recieved',
+ 'desc': 'Matching cookies received',
'snmp': 155,
},
{
{
'name': 'cookie-not-in-reply',
'lambda': '[] { return g_Counters.sum(rec::Counter::cookieNotInReply); }',
- 'desc': 'Authoritative serve sent a reply bnack without cookie',
+ 'desc': 'Authoritative server sent a reply back without cookie',
'snmp': 158,
},
{
- Cookies are stored with an auth IP address as primary index and are generated randomly.
- - If the the does not support cookies, this is marked as such and no cookies will be sent to it
+ - If an auth does not support cookies, it is marked as such and no cookies will be sent to it
for a period of time. When a cookie is sent again, it must be a newly generated one.
- - A cookie is stored together with the local IP (as rec can have many). If a server is to be
+ - A cookie is stored together with the local IP (as rec can have many). If an auth is to be
contacted again, it should use the same bound IP.
- Although it is perfectly fine for a client cookie to live for a long time, this design will
flush entries older that a certain period of time, to avoid an ever growing CookieStore.
-
*/
#include <boost/utility.hpp>
if (ret == LWResult::Result::BindError) {
// BindError is only generated when cookies are active and we failed to bind to a local
// address associated with a cookie, see RFC9018 section 3 last paragraph. We assume the
- // called code alread erased the cookie info.
+ // called code has already erased the cookie info.
// This is the first path that re-iterates the loop
continue;
}