SLAPD-DNSSRV(5)

πŸ’– SLAPD-DNSSRV(5) πŸ’–

okay bestie, you opened the File Formats Manual for slapd-dnssrv, and honestly? it's giving niche icon energy. sit down, grab a πŸ“, and let's get into it.


✨ NAME ✨

slapd-dnssrv β€” DNS SRV referral backend to slapd πŸ¦‹


✨ SYNOPSIS ✨

/etc/openldap/slapd.conf

✨ DESCRIPTION ✨

so the DNSSRV backend for slapd(8) literally serves up referrals based upon SRV resource records held in the Domain Name System. that's the whole vibe. 🌈

⚠️ heads up bestie: this backend is experimental. like, not "experimental but fine", just... experimental. πŸ’€

✨ CONFIGURATION ✨

the DNSSRV backend has no backend nor database specific options. none. zero. nada. πŸ™ˆ

you configure it simply by database dnssrv followed a suffix directive, e.g. suffix "".

so like:

database dnssrv
suffix ""

and that's it, periodt. πŸ’…


✨ ACCESS CONTROL ✨

okay this is the part you actually need to read, bestie, no cap. πŸ”₯

the dnssrv backend does not honor all ACL semantics as described in slapd.access(5). in fact, this backend only implements the search operation when the manageDSAit control (RFC 3296) is used. otherwise, for every operation, a referral (whenever appropriate) or an error is returned. 😭

currently, there is no means to condition the returning of the referral by means of ACLs. no access control is implemented, except for read (=r) access to the returned entries β€” which is actually provided by the frontend. cute, right?

note, however, that the information returned by this backend is collected through the DNS, so it is public by definition. so like... everybody already knows. iykyk. 🌸

✨ FILES ✨

  • /etc/openldap/slapd.conf β€” default slapd configuration file πŸŽ€

✨ SEE ALSO ✨


and that's the page, bestie β€” written by the OpenLDAP crew, shipped as OpenLDAP 2.7.2, dated 2026/10/21. take care of her, she's experimental. πŸ«ΆπŸ‘‘

πŸ“¦ where this page comes from