ldns(3)

💖 ldns — the update-counter girlies 💖

okay bestie, welcome to ldns(3) — the Library Functions Manual section 3 page for the update packet counters. this is a lil family of functions that all live in the same brain cell, and they're here to hand you numbers from an update packet. let's go 🦋

---

✨ NAME ✨

ldns_update_zocount, ldns_update_prcount, ldns_update_upcount, ldns_update_adcount — return update packet counters

like. that's literally the whole job. counters. from update packets. slay 💅

---

✨ SYNOPSIS ✨

#include <stdint.h>
#include <stdbool.h>

#include <ldns/ldns.h>

uint16_t ldns_update_zocount(const ldns_pkt *p);

uint16_t ldns_update_prcount(const ldns_pkt *p);

uint16_t ldns_update_upcount(const ldns_pkt *p);

 ldns_update_adcount();

okay so three of them take a packet and give you back a uint16_t, and then ldns_update_adcount() just… shows up with no arguments at all. not me noticing that. 🙈 anyway, that's exactly how it's written up there, no cap.

---

✨ DESCRIPTION ✨

ldns_update_zocount() — Get the zo count

• p: the packet
• Returns the zo count

ldns_update_prcount() — Get the zo count

• p: the packet
• Returns the pr count

ldns_update_upcount() — Get the zo count

• p: the packet
• Returns the up count

ldns_update_adcount()

(that's it. that's the whole description. she's mysterious. she's iconic. 💀)

real talk bestie — yes, the one-liners for ldns_update_prcount() and ldns_update_upcount() also say "Get the zo count", and yes that's exactly what the page says. i am NOT editing the source material. the zo count said what it said. periodt. 💅

---

✨ AUTHOR ✨

The ldns team at NLnet Labs.

the literal kings and queens of DNS libraries, no big deal 👑

---

✨ REPORTING BUGS ✨

Please report bugs to dns-team@nlnetlabs.nl or on GitHub at https://github.com/NLnetLabs/ldns/issues

found a gremlin? tell the ldns team!! they wanna know!! 🐛✨

---

✨ 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.

okay this part is serious — NO WARRANTY, not even the "it'll probably be fine" kind, not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. like, if it breaks, it's not their problem. i'm just the messenger bestie 🫶

---

✨ SEE ALSO ✨

ldns_update_pkt_new. And perldoc Net::DNS, RFC1034, RFC1035, RFC4033, RFC4034 and RFC4035.

go read those next, iykyk 📚

---

✨ REMARKS ✨

This manpage was automatically generated from the ldns source code.

(so if the vibes are a little unhinged, blame the code generator, not me 🎀)

---

and that's the page!! this came from the ldns library, dated 30 May 2006, and yeah she's still serving after all these years. ldns(3) forever 💜✨ bye bestie, go count some packets!! 🦋