Difference between revisions of "Resolvectl status"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{Draft}} | {{Draft}} | ||
| + | |||
| + | |||
| + | .../... | ||
| + | Link 2 (ens160) | ||
| + | Current Scopes: DNS | ||
| + | DefaultRoute setting: yes | ||
| + | LLMNR setting: yes | ||
| + | MulticastDNS setting: no | ||
| + | DNSOverTLS setting: no | ||
| + | DNSSEC setting: no | ||
| + | DNSSEC supported: no | ||
| + | DNS Servers: 10.10.1.1 | ||
| + | 10.10.1.2 | ||
| + | DNS Domain: yourdomain.com | ||
| + | |||
Revision as of 13:11, 10 November 2020
This article is a Draft. Help us to complete it.
.../...
Link 2 (ens160)
Current Scopes: DNS
DefaultRoute setting: yes
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 10.10.1.1
10.10.1.2
DNS Domain: yourdomain.com
systemctl status systemd-resolved
Related terms
See also
- 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, Pi-hole, NextDNS
Advertising:
