Something worth noting here is that system network daemons, such as
Network Manager will automatically overwrite /etc/resolv.conf as needed
for their purposes.
That might not be what happened here, but with all the different
monolithic daemon services being developed this days it is worth keeping
in mind.
--Ben
On 08/26/2018 05:43 AM, Rich Shepard wrote:
On Sat, 25 Aug 2018, logical american wrote:
This was the problem. The upgrade renamed the current and correctly
configured resolv.conf file as resolv.conf.config and then installed the
empty template file resolv.conf. Why the openSuse install crew couldn't
see a problem here is beyond me.
thanks for that tip, Ken, system is now able to see the world.
Randall,
If Ken had not pointed you to /etc/resolv.conf I would have. All my
portables have a file named /etc/resolv.conf.office which contains the
same DNS entries as the desktops. When away from the office and
connected to
some other LAN that server always takes over and replaces
/etc/resolv.conf
with its own version. So, when I return I just copy the *.office
version and
the host is good to go.
Keep a working copy of /etc/resolv.conf with an extension untouched by
upgrades and copy it to /etc/resolv.conf at the end of any upgrades
you do.
This eliminates DNS issues as a cause of upgrade issues.
Glad you got it quickly fixed,
Rich
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
