some nameserver proposal bits:

unwind.8: point to resolvd(8) for autoconf sources
unwind.conf.5: order preferred list by order of preference
resolvd.8: reformat to read better
route.8: no need to discuss unwind in the nameserver command
umb.4 + sppp.4: note the sending of nameserver proposals

the umb/sppp text is from claudio
tobhe confirmed iked sending proposals when configured to do so

much assistance and ok: florian claudio

do not mention dhclient as a dhcp route message sender

iked(8) is proposing as well

Since sbin/iked/vroute.c r1.13 (sep 2021):
Add client side support for DNS configuration. Use RTM_PROPOSAL_STATIC
route messages to propose the name server to resolvd(8).

resolvd(8) also monitors proposals learned by sppp(4)

OK kn@

mark up the nameserver command;

reference route(8) new nameserver command.

Improve documentation. Try to explain the various inputs that result in
a rewritten resolv.conf, and without being too precise, the order they will
be in the file
discussed with florian and jmc

typo; from Scott Bennett

While I wrote the initial version of resolvd(8) it diverged so much
that it's not appropriate to claim that I wrote it.

Typofix

More accurately describe the DNS proposal sources and reaction by resolvd.
with jmc

Import resold(8), a daemon to rewrite resolv.conf.
prodding deraadt

do not mention dhclient as a dhcp route message sender

iked(8) is proposing as well

Since sbin/iked/vroute.c r1.13 (sep 2021):
Add client side support for DNS configuration. Use RTM_PROPOSAL_STATIC
route messages to propose the name server to resolvd(8).

resolvd(8) also monitors proposals learned by sppp(4)

OK kn@

mark up the nameserver command;

reference route(8) new nameserver command.

Improve documentation. Try to explain the various inputs that result in
a rewritten resolv.conf, and without being too precise, the order they will
be in the file
discussed with florian and jmc

typo; from Scott Bennett

While I wrote the initial version of resolvd(8) it diverged so much
that it's not appropriate to claim that I wrote it.

Typofix

More accurately describe the DNS proposal sources and reaction by resolvd.
with jmc

Import resold(8), a daemon to rewrite resolv.conf.
prodding deraadt

iked(8) is proposing as well

Since sbin/iked/vroute.c r1.13 (sep 2021):
Add client side support for DNS configuration. Use RTM_PROPOSAL_STATIC
route messages to propose the name server to resolvd(8).

resolvd(8) also monitors proposals learned by sppp(4)

OK kn@

mark up the nameserver command;

reference route(8) new nameserver command.

Improve documentation. Try to explain the various inputs that result in
a rewritten resolv.conf, and without being too precise, the order they will
be in the file
discussed with florian and jmc

typo; from Scott Bennett

While I wrote the initial version of resolvd(8) it diverged so much
that it's not appropriate to claim that I wrote it.

Typofix

More accurately describe the DNS proposal sources and reaction by resolvd.
with jmc

Import resold(8), a daemon to rewrite resolv.conf.
prodding deraadt

resolvd(8) also monitors proposals learned by sppp(4)

OK kn@

mark up the nameserver command;

reference route(8) new nameserver command.

Improve documentation. Try to explain the various inputs that result in
a rewritten resolv.conf, and without being too precise, the order they will
be in the file
discussed with florian and jmc

typo; from Scott Bennett

While I wrote the initial version of resolvd(8) it diverged so much
that it's not appropriate to claim that I wrote it.

Typofix

More accurately describe the DNS proposal sources and reaction by resolvd.
with jmc

Import resold(8), a daemon to rewrite resolv.conf.
prodding deraadt

mark up the nameserver command;

reference route(8) new nameserver command.

Improve documentation. Try to explain the various inputs that result in
a rewritten resolv.conf, and without being too precise, the order they will
be in the file
discussed with florian and jmc

typo; from Scott Bennett

While I wrote the initial version of resolvd(8) it diverged so much
that it's not appropriate to claim that I wrote it.

Typofix

More accurately describe the DNS proposal sources and reaction by resolvd.
with jmc

Import resold(8), a daemon to rewrite resolv.conf.
prodding deraadt

Improve documentation. Try to explain the various inputs that result in
a rewritten resolv.conf, and without being too precise, the order they will
be in the file
discussed with florian and jmc

typo; from Scott Bennett

While I wrote the initial version of resolvd(8) it diverged so much
that it's not appropriate to claim that I wrote it.

Typofix

More accurately describe the DNS proposal sources and reaction by resolvd.
with jmc

Import resold(8), a daemon to rewrite resolv.conf.
prodding deraadt

typo; from Scott Bennett

While I wrote the initial version of resolvd(8) it diverged so much
that it's not appropriate to claim that I wrote it.

Typofix

More accurately describe the DNS proposal sources and reaction by resolvd.
with jmc

Import resold(8), a daemon to rewrite resolv.conf.
prodding deraadt

While I wrote the initial version of resolvd(8) it diverged so much
that it's not appropriate to claim that I wrote it.

Typofix

More accurately describe the DNS proposal sources and reaction by resolvd.
with jmc

Import resold(8), a daemon to rewrite resolv.conf.
prodding deraadt

Typofix

More accurately describe the DNS proposal sources and reaction by resolvd.
with jmc

Import resold(8), a daemon to rewrite resolv.conf.
prodding deraadt