There’s this discussion – <YaST not saving or even applying static ip routes>
Please note that, if in ‘/etc/sysconfig/network/config’ the parameter “NETCONFIG_DNS_FORWARDER” isn’t set to the value “resolver” when neither a BIND server nor a dnsmasq server is setup, then various strange DNS resolution effects will be seen on your system –
- Could be a possible cause for the failed resolution of the address “8.8.8.8” to “dns.google” …
And, for completeness – a non-Network-Manager system –
> file /etc/resolv.conf
/etc/resolv.conf: symbolic link to /run/netconfig/resolv.conf
>
> cat /etc/resolv.conf
### /etc/resolv.conf is a symlink to /run/netconfig/resolv.conf
### autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
# NETCONFIG_DNS_STATIC_SEARCHLIST
# NETCONFIG_DNS_STATIC_SERVERS
# NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
# NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
### Call "netconfig update -f" to force adjusting of /etc/resolv.conf.
search fritz.box
nameserver 192.168.178.1
nameserver fda5:b1e5:3a56:0:62b5:8dff:fefe:ca0e
nameserver 2001:9e8:ab40:6e00:62b5:8dff:fefe:ca0e
>