diff options
| author | Michael Biebl <biebl@debian.org> | 2018-06-04 00:07:45 +0200 |
|---|---|---|
| committer | Michael Biebl <biebl@debian.org> | 2018-06-04 00:07:45 +0200 |
| commit | 04bc9e1cd3544445d883ad29ea108c1645c8e7b7 (patch) | |
| tree | d10c354b1b980ca8a7b9e48ec9019e8ed88bde2b /docs/api/html/settings-ipv6.html | |
| parent | ee9c73a923909e23a649407be77e25235d769e25 (diff) | |
New upstream version 1.11.4 upstream/1.11.4
Diffstat (limited to 'docs/api/html/settings-ipv6.html')
| -rw-r--r-- | docs/api/html/settings-ipv6.html | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/api/html/settings-ipv6.html b/docs/api/html/settings-ipv6.html index 5104e422..2f6f8548 100644 --- a/docs/api/html/settings-ipv6.html +++ b/docs/api/html/settings-ipv6.html @@ -8,7 +8,7 @@ <link rel="up" href="ch01.html" title="Configuration Settings"> <link rel="prev" href="settings-ipv4.html" title="ipv4"> <link rel="next" href="settings-ip-tunnel.html" title="ip-tunnel"> -<meta name="generator" content="GTK-Doc V1.27 (XML mode)"> +<meta name="generator" content="GTK-Doc V1.28 (XML mode)"> <link rel="stylesheet" href="style.css" type="text/css"> </head> <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> @@ -75,7 +75,7 @@ <td><pre class="screen">dad-timeout</pre></td> <td><pre class="screen">int32</pre></td> <td><pre class="screen">-1</pre></td> -<td>Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or 3 seconds). A value greater than zero is a timeout in milliseconds.</td> +<td>Timeout in milliseconds used to check for the presence of duplicate IP addresses on the network. If an address conflict is detected, the activation will fail. A zero value means that no duplicate address detection is performed, -1 means the default value (either configuration ipvx.dad-timeout override or zero). A value greater than zero is a timeout in milliseconds. The property is currently implemented only for IPv4.</td> </tr> <tr> <td><pre class="screen">dhcp-hostname</pre></td> @@ -111,13 +111,13 @@ <td><pre class="screen">dns-priority</pre></td> <td><pre class="screen">int32</pre></td> <td><pre class="screen">0</pre></td> -<td>Intra-connection DNS priority. The relative priority to be used when determining the order of DNS servers in resolv.conf. A lower value means that servers will be on top of the file. Zero selects the default value, which is 50 for VPNs and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. For that, just specify the DNS servers in the desired order. When multiple devices have configurations with the same priority, the one with an active default route will be preferred. Note that when using dns=dnsmasq the order is meaningless since dnsmasq forwards queries to all known servers at the same time. Negative values have the special effect of excluding other configurations with a greater priority value; so in presence of at least a negative priority, only DNS servers from connections with the lowest priority value will be used.</td> +<td>DNS servers priority. The relative priority for DNS servers specified by this setting. A lower value is better (higher priority). Zero selects the default value, which is 50 for VPNs and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. When using dns=default, servers with higher priority will be on top of resolv.conf. To prioritize a given server over another one within the same connection, just specify them in the desired order. When multiple devices have configurations with the same priority, the one with an active default route will be preferred. Negative values have the special effect of excluding other configurations with a greater priority value; so in presence of at least a negative priority, only DNS servers from connections with the lowest priority value will be used. When using a DNS resolver that supports split-DNS as dns=dnsmasq or dns=systemd-resolved, each connection is used to query domains in its search list. Queries for domains not present in any search list are routed through connections having the '~.' special wildcard domain, which is added automatically to connections with the default route (or can be added manually). When multiple connections specify the same domain, the one with the highest priority (lowest numerical value) wins. If a connection specifies a domain which is subdomain of another domain with a negative DNS priority value, the subdomain is ignored.</td> </tr> <tr> <td><pre class="screen">dns-search</pre></td> <td><pre class="screen">array of string</pre></td> <td><pre class="screen">[]</pre></td> -<td>Array of DNS search domains.</td> +<td>Array of DNS search domains. Domains starting with a tilde ('~') are considered 'routing' domains and are used only to decide the interface over which a query must be forwarded; they are not used to complete unqualified host names.</td> </tr> <tr> <td><pre class="screen">gateway</pre></td> @@ -204,6 +204,6 @@ </div> </div> <div class="footer"> -<hr>Generated by GTK-Doc V1.27</div> +<hr>Generated by GTK-Doc V1.28</div> </body> </html> \ No newline at end of file |