diff options
author | Oskar Roesler <o.roesler@oscloud.info> | 2023-02-21 01:20:10 +0100 |
---|---|---|
committer | Daniel Wagner <wagi@monom.org> | 2023-04-11 09:05:57 +0200 |
commit | 9cf2cc3844e486a81c5c118de4bcbde3489e097a (patch) | |
tree | 38c4346086c0da919f303cfc617941bde10cea5e | |
parent | 066a1acc0de9d8bf121420b73c2ee1a8e30cc3a4 (diff) | |
download | connman-9cf2cc3844e486a81c5c118de4bcbde3489e097a.tar.gz |
doc: Update connman(8) manpage on the --nodnsproxy option.
The --nodnsproxy option documentation left out that ConnMan will fall
back to creating a resolv.conf on startup. This gets fixed by this.
-rw-r--r-- | doc/connman.8.in | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/doc/connman.8.in b/doc/connman.8.in index 0617cfbf..ffee8d3f 100644 --- a/doc/connman.8.in +++ b/doc/connman.8.in @@ -95,9 +95,11 @@ to itself by setting nameserver to 127.0.0.1 in \fBresolv.conf\fP(5) file or leave DNS management to an external entity, such as systemd-resolved. If this is not desired and you want that all programs call directly some DNS server, then you can use the \fB--nodnsproxy\fP -option. If this option is used, then ConnMan is not able to cache the -DNS queries because the DNS traffic is not going through ConnMan and that -can cause some extra network traffic. +option. ConnMan then figures out the DNS server and search domain +on startup and sets them in \fBresolv.conf\fP(5). If this option is +used, then ConnMan is not able to cache the DNS queries because the DNS +traffic is not going through ConnMan and that can cause some extra +network traffic. .SH SEE ALSO .BR connmanctl (1), \ connman.conf (5), \ connman-service.config (5), \c .BR \ connman-vpn (8) |