SSH • TLS • HTTPS • Network Monitoring
lo UNKNOWN 127.0.0.1/8 eth0 UP 173.212.203.211/24 docker0 DOWN 172.17.0.1/16 br-25e3e00f5f1c UP 172.18.0.1/16 vethcd23a7c@if2 UP veth31aff88@if2 UP vethaf30214@if2 UP br-82994b693097 UP 172.19.0.1/16 vethb8d0a83@if2 UP veth5a7f5db@if2 UP veth53c2c1b@if2 UP tailscale0 UNKNOWN 100.74.74.35/32
default via 173.212.203.1 dev eth0 proto static onlink
# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8). # Do not edit. # # This file might be symlinked as /etc/resolv.conf. If you're looking at # /etc/resolv.conf and seeing this text, you have followed the symlink. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "resolvectl status" to see details about the uplink DNS servers # currently in use. # # Third party programs should typically not access this file directly, but only # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a # different way, replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 options edns0 trust-ad search invalid tailb87455.ts.net