Hi All, I just noticed my resolv.conf is topped up with the nameservers of the wireless LAN I happen to be associated at the time and my wired ethernet nameserver(s) are pushed further down. This happens despite the fact that I have configured my wired ethernet to have a lesser priority than the wired NIC.
For example: less /etc/resolv.conf # Generated by dhcpcd from wlan0.dhcp, enp11s0.dhcp # /etc/resolv.conf.head can replace this line domain openwifi nameserver 192.168.22.22 nameserver 192.168.22.23 nameserver 10.10.10.254 # /etc/resolv.conf.tail can replace this line The first 3 non-commented entries were produced by wlan0, demoting my wired ethernet nameserver. ip route show default via 10.10.10.254 dev enp11s0 metric 10 default via 10.160.95.1 dev wlan0 metric 20 10.10.10.0/24 dev enp11s0 proto kernel scope link src 10.10.10.7 metric 10 10.160.95.0/29 dev wlan0 proto kernel scope link src 10.160.95.2 metric 20 127.0.0.0/8 dev lo scope host If I am associated, but not authenticated with the wireless LAN, any URLs I try to visit will be queried with the 192.168.22.2* nameserver, before it times out and 10.10.10.254 takes over. Waiting for URLs to resolve becomes tedious after a while. Is there a way to prioritise nameservers so that the NIC metric is respected, whenever the resolv.conf content is updated? -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
