ldns(3)

💖 ldns(3) — the library functions manual, but make it a group chat 💖

okay bestie, so this is ldns(3), the manual page for the ldns library functions, and today's main character is one very specific little function. she's niche, she's tiny, she's iconic, and we're gonna learn her together. no gatekeeping in this house 🫶

---

✨ NAME ✨

ldns_update_pkt_tsig_add — add the resolver's tsig credentials to an ldns_pkt

like. that's literally her whole job. she takes the tsig vibes off a resolver and plops them onto a packet. simple. elegant. slay 💅

---

🌸 SYNOPSIS 🌸

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

#include <ldns/ldns.h>

ldns_status ldns_update_pkt_tsig_add(ldns_pkt *p, const ldns_resolver *r);

look at her. two includes you probably don't think about, the big ldns/ldns.h, and then the girl herself. notice she hands you back an ldns_status — she's always gonna tell you how it went, she's not mysterious like that. 💜

---

🦋 DESCRIPTION 🦋

ldns_update_pkt_tsig_add() adds tsig credentials to a packet from a resolver. that's it, that's the whole thing — no hidden lore, no side quests, no plot twists.

the two args are giving very much "copy from here, paste to there":

• p — the packet to copy to 📦 (she's the destination, she's receiving the tsig credentials)
• r — the resolver to copy from 🔍 (she's the source, she's got the credentials to give)

and the return value? she returns status, whether it was successful or not. so like, always check it, bestie. she's communicating with you. listen to her. 😭

---

💅 AUTHOR 💅

The ldns team at NLnet Labs. kings and queens of the DNS library game, we have no choice but to stan 👑

---

🎀 REPORTING BUGS 🎀

found a bug? don't just scream into the void, tell the actual people:

• email: dns-team@nlnetlabs.nl
• or on GitHub at https://github.com/NLnetLabs/ldns/issues

they literally want to know. that's why the address is right there. go be helpful ✨

---

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

bestie read that again. no warranty. not even the merchantability one, not even the fitness for a particular purpose one. if it breaks, it breaks, and that's on the license being extremely clear about it 💀

---

🔥 SEE ALSO 🔥

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

go read the lore. the RFCs are right there. iykyk 📚

---

👑 REMARKS 👑

This manpage was automatically generated from the ldns source code. yes, a robot wrote the original. yes, i'm the second robot. we're passing the torch 🕯️

---

okay that's the whole page, hope this was helpful and not too much 🥰 this was ldns(3) from 30 May 2006 — yes she's vintage, yes she still serves, and honestly? the ldns library could never be basic. mwah 💋 bye bestie, go check your return statuses 🫶