lubux schrieb:
Chianti schrieb:
In der /etc/interfaces und resolv.conf steht aber der richtige DNS-Server (kein Netplan).
Wie sind die Ausgaben von:
cat /etc/resolv.conf
{{{
nameserver 192.168.178.XX
cat /etc/nsswitch.conf
passwd: compat systemd
group: compat systemd
shadow: compat
gshadow: files
hosts: files dns
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
host -t A heise.de 1.1.1.1
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases:
heise.de has address 193.99.144.80
host -t A heise.de
;; connection timed out; no servers could be reached
nc -zv 1.1.1.1 53
Connection to 1.1.1.1 53 port [tcp/domain] succeeded!
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 50:3e:aa:09:8d:e4 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.16/24 brd 192.168.178.255 scope global enp1s0
valid_lft forever preferred_lft forever
inet6 fe80::523e:aaff:fe09:8de4/64 scope link
valid_lft forever preferred_lft forever
3: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 70:85:c2:b0:13:d0 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.15/24 brd 192.168.178.255 scope global enp3s0
valid_lft forever preferred_lft forever
inet6 fe80::7285:c2ff:feb0:13d0/64 scope link
valid_lft forever preferred_lft forever
ip n s
192.168.178.1 dev enp3s0 lladdr 44:4e:6d:ea:5e:93 REACHABLE
192.168.178.108 dev enp3s0 lladdr d8:50:e6:d2:93:b6 REACHABLE
192.168.178.17 dev enp3s0 lladdr b8:27:eb:6c:93:e0 REACHABLE
192.168.178.40 dev enp3s0 lladdr a0:02:dc:24:50:3e STALE
}}}
?
Danke!