summaryrefslogtreecommitdiffstats
path: root/upstream/opensuse-tumbleweed/man5/org.freedesktop.resolve1.5
diff options
context:
space:
mode:
Diffstat (limited to 'upstream/opensuse-tumbleweed/man5/org.freedesktop.resolve1.5')
-rw-r--r--upstream/opensuse-tumbleweed/man5/org.freedesktop.resolve1.558
1 files changed, 57 insertions, 1 deletions
diff --git a/upstream/opensuse-tumbleweed/man5/org.freedesktop.resolve1.5 b/upstream/opensuse-tumbleweed/man5/org.freedesktop.resolve1.5
index 7810193a..2046567f 100644
--- a/upstream/opensuse-tumbleweed/man5/org.freedesktop.resolve1.5
+++ b/upstream/opensuse-tumbleweed/man5/org.freedesktop.resolve1.5
@@ -1,5 +1,5 @@
'\" t
-.TH "ORG\&.FREEDESKTOP\&.RESOLVE1" "5" "" "systemd 254" "org.freedesktop.resolve1"
+.TH "ORG\&.FREEDESKTOP\&.RESOLVE1" "5" "" "systemd 255" "org.freedesktop.resolve1"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
@@ -420,6 +420,32 @@ set) so that all settings take effect during the full time the network interface
The
\fBRevertLink()\fR
method may be used to revert all per\-link settings described above to the defaults\&.
+.PP
+The
+\fBFlushCaches()\fR
+flushes all resource record caches maintained by the resolver, and ensures that any subsequent lookups re\-request their responses from their sources\&.
+.PP
+The
+\fBResetServerFeatures()\fR
+flushes any feature information learned about remote DNS servers\&. This ensures that subsequent lookups will be initially attempted at the highest DNS protocol feature level again, possibly requiring a (potentially slow) downgrade cycle to recognize the supported feature level again\&.
+.PP
+The
+\fBRegisterService()\fR
+method may be used to register a DNS\-SD service on the host\&. This functionality is closely related to the functionality provided by
+\fBsystemd.dnssd\fR(5)
+files\&. It takes a server identifier string as first parameter (this is jus a local identifier, and should be chosen so that it neither collides with the basename of
+*\&.dnssd
+files nor with names chosen by other IPC clients)\&. It also takes a name template string for the DNS\-SD service name visible on the network\&. This string is subject to specifier expansation, as documented for the
+\fIName=\fR
+setting in
+*\&.dnssd
+files\&. It also takes a service type string containing the DNS\-SD service type, as well as an IP port, a priority/weight pair for the DNS\-SD SRV record\&. Finally, it takes an array of TXT record data\&. It returns an object path which may be used as handle to the registered service\&.
+.PP
+The
+\fBUnregisterService()\fR
+method undoes the effect of
+\fBRegisterService()\fR
+and deletes a DNS\-SD service previously created via IPC again\&.
.sp
.it 1 an-trap
.nr an-no-space-flag 1
@@ -646,6 +672,10 @@ property reports whether the stub listener on port 53 is enabled\&. Possible val
(only the UDP listener is enabled), and
"tcp"
(only the TCP listener is enabled)\&.
+.PP
+The
+\fIDNSSECNegativeTrustAnchors\fR
+property contains a list of recognized DNSSEC negative trust anchors and contains a list of domains\&.
.SH "LINK OBJECT"
.sp
.if n \{\
@@ -781,26 +811,36 @@ interface) may return some of the following errors:
\fBorg\&.freedesktop\&.resolve1\&.NoNameServers\fR
.RS 4
No suitable DNS servers were found to resolve a request\&.
+.sp
+Added in version 246\&.
.RE
.PP
\fBorg\&.freedesktop\&.resolve1\&.InvalidReply\fR
.RS 4
A response from the selected DNS server was not understood\&.
+.sp
+Added in version 246\&.
.RE
.PP
\fBorg\&.freedesktop\&.resolve1\&.NoSuchRR\fR
.RS 4
The requested name exists, but there is no resource record of the requested type for it\&. (This is the DNS NODATA case)\&.
+.sp
+Added in version 246\&.
.RE
.PP
\fBorg\&.freedesktop\&.resolve1\&.CNameLoop\fR
.RS 4
The look\-up failed because a CNAME or DNAME loop was detected\&.
+.sp
+Added in version 246\&.
.RE
.PP
\fBorg\&.freedesktop\&.resolve1\&.Aborted\fR
.RS 4
The look\-up was aborted because the selected protocol became unavailable while the operation was ongoing\&.
+.sp
+Added in version 246\&.
.RE
.PP
\fBorg\&.freedesktop\&.resolve1\&.NoSuchService\fR
@@ -808,43 +848,59 @@ The look\-up was aborted because the selected protocol became unavailable while
A service look\-up was successful, but the
\fBSRV\fR
record reported that the service is not available\&.
+.sp
+Added in version 246\&.
.RE
.PP
\fBorg\&.freedesktop\&.resolve1\&.DnssecFailed\fR
.RS 4
The acquired response did not pass DNSSEC validation\&.
+.sp
+Added in version 246\&.
.RE
.PP
\fBorg\&.freedesktop\&.resolve1\&.NoTrustAnchor\fR
.RS 4
No chain of trust could be established for the response to a configured DNSSEC trust anchor\&.
+.sp
+Added in version 246\&.
.RE
.PP
\fBorg\&.freedesktop\&.resolve1\&.ResourceRecordTypeUnsupported\fR
.RS 4
The requested resource record type is not supported on the selected DNS servers\&. This error is generated for example when an RRSIG record is requested from a DNS server that does not support DNSSEC\&.
+.sp
+Added in version 246\&.
.RE
.PP
\fBorg\&.freedesktop\&.resolve1\&.NoSuchLink\fR
.RS 4
No network interface with the specified network interface index exists\&.
+.sp
+Added in version 246\&.
.RE
.PP
\fBorg\&.freedesktop\&.resolve1\&.LinkBusy\fR
.RS 4
The requested configuration change could not be made because
\fBsystemd-networkd\fR(8), already took possession of the interface and supplied configuration data for it\&.
+.sp
+Added in version 246\&.
.RE
.PP
\fBorg\&.freedesktop\&.resolve1\&.NetworkDown\fR
.RS 4
The requested look\-up failed because the system is currently not connected to any suitable network\&.
+.sp
+Added in version 246\&.
.RE
.PP
\fBorg\&.freedesktop\&.resolve1\&.DnsError\&.NXDOMAIN\fR, \fBorg\&.freedesktop\&.resolve1\&.DnsError\&.REFUSED\fR, \&.\&.\&.
.RS 4
The look\-up failed with a DNS return code reporting a failure\&. The error names used as suffixes here are defined in by IANA in
\m[blue]\fBDNS\ \&RCODEs\fR\m[]\&\s-2\u[4]\d\s+2\&.
+.sp
+Added in version 246\&.
.RE
.SH "EXAMPLES"
.PP