ldns(3)
π ldns(3) β the ldns library, bestie edition π¦
okay so this is a page from the ldns(3) manual, and it's specifically about one little function that wants to be getaddrinfo() when it grows up. it's giving "library functions manual" energy and we are OBSESSED. let's get into it π
β¨ NAME β¨
ldns_getaddrinfo β mimic libc getaddrinfo
like. it literally says "mimic". it's a tribute act. a cover band. and honestly? it ate. π€
πΈ SYNOPSIS πΈ
#include <stdint.h>
#include <stdbool.h>
#include <ldns/ldns.h>
uint16_t ldns_getaddrinfo(ldns_resolver *res, const ldns_rdf *node,
ldns_rr_class c, ldns_rr_list **list);
no cap, those includes are mandatory, she's not optional about it π
π§ DESCRIPTION π§
so ldns_getaddrinfo() is a wrapper function for ldns_get_rr_list_name_by_addr and ldns_get_rr_list_addr_by_name. it's basically the group chat admin of those two β it just handles the vibes so you don't have to π
and yeah, the name is straight up borrowed from the getaddrinfo() library call. it tries to mimic that call, but β and this is the important part, bestie β without the lowlevel stuff. so it's getaddrinfo() but in a cute little cardigan. π
here's the rundown of the arguments, periodt:
resβ the resolver. if this value isNULLthen a resolver will be created byldns_getaddrinfo. yes, it'll just make one for you. main character behaviour fr fr πnodeβ the name or ip address to look up. that's the thing you're curious about πcβ the class to look in. y'know, the class class πlistβ put the found RR's in this list. she's your output bucket, hand her over π
Returns the number of RR found. that's the whole point. that's the answer. count it and slay. β¨
π AUTHOR π
The ldns team at NLnet Labs. icons only, we stan π«Ά
π REPORTING BUGS π
found a bug? not me ignoring it π please report bugs to dns-team@nlnetlabs.nl or on GitHub at https://github.com/NLnetLabs/ldns/issues β they will look at it, and honestly the GitHub issue tracker is lowkey the move π
π 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 so read that again bestie. NO WARRANTY. not even the MERCHANTABILITY one. not even the FITNESS FOR A PARTICULAR PURPOSE one. zero. nada. she is free and she is unbothered and if she breaks something that is legally, genuinely, for-real not her problem π use at your own vibe.
π₯ SEE ALSO π₯
go read your RFCs, iykyk π
π REMARKS π
This manpage was automatically generated from the ldns source code. so no human wrote this, a machine did, and it still understood the assignment. iconic, honestly. π€β¨
and that's the whole page, bestie β this was ldns(3) from the ldns source, dated 30 May 2006, and it's been serving ever since. mwah π go write some RRs π¦πΈ
π¦ 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