1DOMAIN(8) InterNetNews Documentation DOMAIN(8)
2
3
4
6 domain - nnrpd domain resolver
7
9 domain domain-name
10
12 This program can be used in readers.conf to grant access based on the
13 subdomain part of the remote hostname. In particular, it only returns
14 success if the remote hostname ends in domain-name. (A leading dot on
15 domain-name is optional; even without it, the argument must match on
16 dot-separated boundaries). The "username" returned is whatever initial
17 part of the remote hostname remains after domain-name is removed. It
18 is an error if there is no initial part (that is, if the remote
19 hostname is exactly the specified domain-name).
20
22 The following readers.conf(5) fragment grants access to hosts with
23 internal domain names:
24
25 auth internal {
26 res: "domain .internal"
27 default-domain: "example.com"
28 }
29
30 access internal {
31 users: "*@example.com"
32 newsgroups: example.*
33 }
34
35 Access is granted to the example.* groups for all connections from
36 hosts that resolve to hostnames ending in ".internal"; a connection
37 from "foo.internal" would match access groups as "foo@example.com"
38 identity.
39
41 It seems the code does not confirm that the matching part is actually
42 at the end of the remote hostname (e.g., "domain: example.com" would
43 match the remote host "foo.example.com.org" by ignoring the trailing
44 ".org" part).
45
46 Does this resolver actually provide any useful functionality not
47 available by using wildcards in the readers.conf(5) hosts parameter?
48 If so, the example above should reflect this functionality.
49
51 This documentation was written by Jeffrey M. Vinocur <jeff@litech.org>.
52
54 nnrpd(8), readers.conf(5)
55
56
57
58INN 2.7.1 2023-03-07 DOMAIN(8)