On 2015/11/04 10:56, Raf Czlonka wrote:
> @@ -141,7 +145,7 @@ If using a caching name server, add the
> Relevant
> .Xr rc.conf 8
> variables:
> -.Va named_flags
> +.Va nsd_flags
> and
> .Va unbound_flags .
Hmm. This section is a bit weird.
If you are using a name server, check the /etc/resolv.conf file. It may
look something like:
domain nts.umn.edu
nameserver 128.101.101.101
nameserver 134.84.84.84
search nts.umn.edu. umn.edu.
lookup file bind
If using a caching name server, add the line "nameserver 127.0.0.1"
first.
Most name servers that people will list in resolv.conf are caching
name servers, and they don't need to be on localhost..
Relevant rc.conf(8) variables: named_flags and unbound_flags.
Just going by the section name "Domain Name Server (DNS)" nsd_flags
fits, but the text only talks about resolvers. Would it make any kind
of sense to split this into "DNS resolver" and "Authoritative DNS"?
There is also rebound(8) to mention, which runs on localhost, but
is not a caching server.
> @@ -224,6 +228,7 @@ variables:
> .Ss Routing Daemons
> Various daemons for managing routing tables are available:
> .Xr bgpd 8 ,
> +.Xr eigrpd 8 ,
> .Xr ospfd 8 ,
> and
> .Xr ripd 8 .
This text makes it look like an exhaustive list. I'd either add
the word "including" or add the others - in either case ospf6d could
do with being added.
Might be better, though, to go with something like "Various daemons
for managing dynamic routing are available" (i.e. not saying "routing
tables") and include ldpd.
