Difference between revisions of "Systemd-resolve --status"
Jump to navigation
Jump to search
| Line 29: | Line 29: | ||
* <code>[[netplan]]</code> | * <code>[[netplan]]</code> | ||
* <code>[[systemctl status systemd-resolved]]</code> | * <code>[[systemctl status systemd-resolved]]</code> | ||
| + | * <code>[[resolvectl status]]</code> | ||
== See also == | == See also == | ||
Revision as of 13:13, 10 November 2020
systemd-resolve --status
Global
.../...
Link 3 (docker0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 2 (enp1s0)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: XX.xx.xx.XX
xx.XX.xx.XX
DNS Domain: yourdomain.com
Ubuntu and Raspberry Pi OS
systemd-resolve --status Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.
Related terms
See also
systemd-resolve:systemd-resolve --help,systemd-resolve --status,/etc/systemd/resolved.conf,systemd-resolve --statistics,resolvectl status,journalctl -u systemd-resolved,systemd-resolve --set-dns,systemctl start systemd-resolved- DNS: Linux DNS, IP,
systemd-resolve,/etc/hosts,whois, Domain registrar,dig,host,nslookup,scutil --dnsdnsmasq,bind,delv,.local,.internal, .onion, FQDN, TTL,/etc/resolv.conf,/etc/systemd/resolved.conf,dscacheutil(macOS),hostname, hostnamectl,bind,resolvectl status, DNS sinkhole, Domain name server, LLMNR, Resource records:MX, TXT, NS, CAA, SSHFP, Apex, CNAME, Wildcard DNS records, Subdomain, /etc/nsswitch.conf,1.1.1.1,8.8.8.8, CoreDNS, dnsPolicy:, Google Public DNS, DNS caches, Kubernetes ExternalDNS, DNS forwarding, IDNA2008, DNS-1035, Domain name registrars, Split-view DNS
Advertising:
