New upstream version 1.45.90 upstream/1.45.90

1 files changed, 13 insertions, 2 deletions

diff --git a/docs/api/html/NetworkManager-dispatcher.html b/docs/api/html/NetworkManager-dispatcher.html
index 88ed3634..b8ef62c3 100644
--- a/docs/api/html/NetworkManager-dispatcher.html
+++ b/docs/api/html/NetworkManager-dispatcher.html
@@ -51,8 +51,9 @@
       device an operation just happened on, and second the action. For device actions,
       the interface is the name of the kernel interface suitable for IP configuration.
       Thus it is either VPN_IP_IFACE, DEVICE_IP_IFACE, or DEVICE_IFACE, as applicable.
-      For the <code class="varname">hostname</code> action the device name is always <code class="literal">"none"</code>
-      and for <code class="varname">connectivity-change</code> it is empty.
+      For the <code class="varname">hostname</code> action the device name is always
+      <code class="literal">"none"</code>. For <code class="varname">connectivity-change</code> and
+      <code class="varname">dns-change</code> it is empty.
     </p>
 <p>The actions are:</p>
 <div class="variablelist"><table border="0" class="variablelist">
@@ -158,6 +159,16 @@
           The connection was reapplied on the device.
         </p></td>
 </tr>
+<tr>
+<td><p><span class="term"><code class="varname">dns-change</code></span></p></td>
+<td><p>
+            The DNS configuration has changed. This action is raised even if
+            NetworkManager is configured to not manage resolv.conf (for example,
+            via dns=none). In such case, the dispatch script can discover the
+            DNS configuration provided by currently active connections by
+            looking at file <code class="filename">/run/NetworkManager/resolv.conf</code>
+        </p></td>
+</tr>
 </tbody>
 </table></div>
 <p>