Comment # 9 on bug 1114569 from Rihards Olups

Had Tumbleweed system (version around 2019-02) with this problem. Here's data I
collected/recall.

1. Connecting to another wifi, switching wifi on/off or restarting the network
service made no difference (I believe a full system restart was also
attempted).

2. netconfig complained about /etc/resolv.conf being modified. At that time,
resolv.conf was as follows (I did not collect information on file metadata or
unprintable characters, unfortunately).

### /etc/resolv.conf file 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.
#
# Note: Manual change of this file disables netconfig too, but
# may get lost when this file contains comments or empty lines
# only, the netconfig settings are same with settings in this
# file and in case of a "netconfig update -f" call.
#
### Please remove (at least) this line when you modify the file!

3. netconfig generated /etc/resolv.conf.netconfig . When this file was moved to
/etc/netconfig, it was still considered modified, and was not modified when
switching between different wifi networks.

4. Connecting to one of the networks sometimes resulted in an IPv6 DNS entry in
the file, sometimes did not. I do not know whether this could have had any
impact on the problem.