summaryrefslogtreecommitdiff
path: root/src/resolve/resolved.conf.in
diff options
context:
space:
mode:
authorSuraj Krishnan <72937403+surajkrishnan14@users.noreply.github.com>2022-04-26 17:09:02 -0500
committerLuca Boccassi <luca.boccassi@gmail.com>2022-09-09 09:22:57 +0100
commitcb456374e096f0ebe9b70d7ddd98e16a4be24ee6 (patch)
tree514bb0753834490ab81e8a21669abe28ba66205a /src/resolve/resolved.conf.in
parent761787fc88aff81f3e97da07ac829f431479fe0b (diff)
downloadsystemd-cb456374e096f0ebe9b70d7ddd98e16a4be24ee6.tar.gz
Implement DNS notifications from resolved via varlink
* The new varlink interface exposes a method to subscribe to DNS resolutions on the system. The socket permissions are open for owner and group only. * Notifications are sent to subscriber(s), if any, after successful resolution of A and AAAA records. This feature could be used by applications for auditing/logging services downstream of the resolver. It could also be used to asynchronously update the firewall. For example, a system that has a tightly configured firewall could open up connections selectively to known good hosts based on a known allow-list of hostnames. Of course, updating the firewall asynchronously will require other design considerations (such as queueing packets in the user space while a verdict is made). See also: https://lists.freedesktop.org/archives/systemd-devel/2022-August/048202.html https://lists.freedesktop.org/archives/systemd-devel/2022-February/047441.html
Diffstat (limited to 'src/resolve/resolved.conf.in')
-rw-r--r--src/resolve/resolved.conf.in1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/resolve/resolved.conf.in b/src/resolve/resolved.conf.in
index 6d4176df52..1f36e9cb2b 100644
--- a/src/resolve/resolved.conf.in
+++ b/src/resolve/resolved.conf.in
@@ -32,3 +32,4 @@
#DNSStubListenerExtra=
#ReadEtcHosts=yes
#ResolveUnicastSingleLabel=no
+#Monitor=no