DOMAIN(8)

💖 NAME 💖

okay so this is domain — the nnrpd domain resolver, straight out of the InterNetNews documentation, section 8 of the manual, bestie. she's a tiny little auth helper and she's got a very specific job. ✨

---

🦋 SYNOPSIS 🦋

domain domain-name

that's it. one argument. she's low maintenance. 💅

---

🌸 DESCRIPTION 🌸

so here's the vibe: you can drop this program into readers.conf to grant access based on the subdomain part of the remote hostname. main character energy for subdomains only. 👑

the important bit — it only returns success if the remote hostname ends in domain-name. no ending, no entry. periodt.

a couple of small but crucial details: 🎀

• a leading dot on domain-name is optional — and even if you don't put one there, the argument still has to match on dot-separated boundaries. so like, boundaries matter, iykyk.
• the "username" it hands back is whatever initial part of the remote hostname remains after domain-name gets removed.
• and it is an error if there's no initial part left — meaning if the remote hostname is exactly the specified domain-name, she's not doing that. that's a whole error. 😭

---

🧚 EXAMPLE 🧚

here's a readers.conf(5) fragment that grants access to hosts with internal domain names — copy it exactly, bestie, don't freestyle:

auth internal {
    res: "domain .internal"
    default-domain: "example.com"
}

access internal {
    users: "*@example.com"
    newsgroups: example.*
}

so what's happening here? access is granted to the example.* groups for all connections from hosts that resolve to hostnames ending in ".internal". and like, concretely: a connection from "foo.internal" would match access groups as a "foo@example.com" identity. slay. 🫶

---

💀 BUGS 💀

okay girlies, gather round, we gotta be honest about a couple of things. 🙈

• it seems the code does not confirm that the matching part is actually at the end of the remote hostname. like for real — e.g. "domain: example.com" would match the remote host "foo.example.com.org" by ignoring the trailing ".org" part. yeah. not ideal. 😭
• and the big question the docs literally ask: does this resolver actually provide any useful functionality that you couldn't already get by using wildcards in the readers.conf(5) hosts parameter? if so, the example above should reflect this functionality. so like... open question, fr fr. 🤔

no cap, those are the original doc's own words — I'm just delivering the tea, not making new claims. 💅

---

🌈 HISTORY 🌈

this documentation was written by Jeffrey M. Vinocur <jeff@litech.org>. credit where credit's due, bestie. 💜

---

⭐ SEE ALSO ⭐

• nnrpd(8)
• readers.conf(5)

---

and that's the whole page, bestie! 🎀 this little gem is from INN 2.7.4, dated 2023-03-07 — so go forth, resolve those domains, and remember: dot-separated boundaries are not a suggestion. 💖✨