ldns(3)
π NAME π
ldns_update_set_zocount, ldns_update_set_prcount, ldns_update_set_upcount, ldns_update_set_adcount β bestie, these are the little gremlins that set the update packet counters. That's the whole job. They set counters. On packets. Periodt. β¨
This is page ldns(3) from the Library Functions Manual, and no, we are not skipping a single flag, iykyk.
πΈ SYNOPSIS πΈ
#include <stdint.h>
#include <stdbool.h>
#include <ldns/ldns.h>
ldns_update_set_zocount();
void ldns_update_set_prcount(ldns_pkt *p, uint16_t c);
void ldns_update_set_upcount(ldns_pkt *p, uint16_t c);
void ldns_update_set_adcount(ldns_pkt *p, uint16_t c);
Look at that. Four whole functions. Three of them take arguments, one of them is just vibing with nothing. We love a mysterious queen. π
π¦ DESCRIPTION π¦
okay so, grab your packet and let's go through these one by one, because each one is doing its own little thing.
ldns_update_set_zocount()
That's it. That's the entry. No params listed, no explanation given, it's just there, existing, being iconic and undocumented. We respect the mystery. π
ldns_update_set_prcount()
This one sets the pr count. Here's the tea on its arguments:
- p β the packet π
- c β the pr count to set
ldns_update_set_upcount()
This one sets the up count. Arguments:
- p β the packet π
- c β the up count to set
ldns_update_set_adcount()
And this one sets the ad count</ad>. Arguments:
- p β the packet π
- c β the ad count to set
Three nearly identical functions, three different counters, zero notes. It's giving "I have one job and I do it flawlessly." π₯
π AUTHOR π
The ldns team at NLnet Labs. Absolute legends, we thank them for their service. π«Ά
π REPORTING BUGS π
Found something cursed? Do NOT suffer in silence, bestie. Report it:
- email:
dns-team@nlnetlabs.nl - or on GitHub at
https://github.com/NLnetLabs/ldns/issues
Fr fr, they want to know. Bugs are not a personality trait you have to carry alone. π
β COPYRIGHT β
Copyright (c) 2004 - 2006 NLnet Labs.
Licensed under the BSD License. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Translation: it is what it is, and legally they are not responsible for what it is. π
π SEE ALSO π
Homework. Go read them. Or at least open the tabs. We both know how this works. π
π§ REMARKS π§
This manpage was automatically generated from the ldns source code. No human wrote it by hand, which honestly explains a lot about the ldns_update_set_zocount() situation. π
and that's the whole page, babes β this one's dated 30 May 2006, so it's older than most of us and still serving cunt in the ldns library, from the Library Functions Manual, ldns(3). slay, stay safe, and set those counters responsibly π
β¨π
π¦ where this page comes from
- alpine 3.22: ldns-doc 1.8.4-r0 Β· BSD-3-Clause
- alpine 3.23: ldns-doc 1.8.4-r1 Β· BSD-3-Clause
- alpine 3.24: ldns-doc 1.8.4-r1 Β· BSD-3-Clause
- arch rolling: ldns 1.9.2-1 Β· custom:BSD
- debian trixie: libldns-dev 1.8.4-2+b1
- fedora 43: ldns-devel 1.8.4-8.fc43 Β· BSD-3-Clause
- fedora 43: ldns-devel 1.8.4-8.fc43 Β· BSD-3-Clause
- fedora 43: ldns-devel 1.9.2-1.fc43 Β· BSD-3-Clause
- fedora 43: ldns-devel 1.9.2-1.fc43 Β· BSD-3-Clause
- fedora 44: ldns-devel 1.9.0-2.fc44 Β· BSD-3-Clause
- fedora 44: ldns-devel 1.9.0-2.fc44 Β· BSD-3-Clause
- fedora 44: ldns-devel 1.9.2-1.fc44 Β· BSD-3-Clause
- fedora 44: ldns-devel 1.9.2-1.fc44 Β· BSD-3-Clause
- nixos 26.05: ldns 1.9.2
- nixpkgs unstable: ldns 1.9.2
- opensuse-leap 16.0: ldns-devel 1.8.4-160000.3.1 Β· BSD-3-Clause
- opensuse-leap 16.0: ldns-devel 1.8.4-160000.3.1 Β· BSD-3-Clause
- opensuse-leap 16.0: ldns-devel 1.8.4-160000.3.1 Β· BSD-3-Clause
- opensuse-leap 16.0: ldns-devel 1.8.4-160000.3.1 Β· BSD-3-Clause
- ubuntu questing: libldns-dev 1.8.4-2build1
- ubuntu resolute: libldns-dev 1.8.4-2build3
- ubuntu stonking: libldns-dev 1.9.2-1ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms