Odd DNS issue after update

[jiml8]

Earlier today, an update came through. I was busy, so I looked at it very briefly, then permitted it to happen...and I do not recall what was in it except that it DID update Kate among other things. Didn't look serious...

Well, I browse through TOR almost exclusively, so it was actually quite a few hours before I noticed that any attempt to browse directly (not using TOR) failed with what was obviously a DNS problem. (TOR provides its own DNS within the TOR network, so when I browse through TOR, I connect to the TOR entry portal and everything happens inside the network, thus my ISP does not have even DNS lookup packets to see where I am going).

A quick look at /etc/resolv.conf showed that my DNS entries had been deleted. However, they did properly remain configured in the Mageia control center. I replaced the DNS entries using cat and immediately was up and running again.

Now, I have no idea what happened here, and I only assume something in the update did it. I have not been messing with any networking on this host for quite awhile here; I am positive I did not do it.

But, I am mentioning it here in case others have experienced the same thing.

[nigelc]

On my system the dns settings are done by the modem.
The resolv.conf looks like this:

Code: Select all

[nigel@endor ~]$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.1.1
search Home


[gohlip]

If problem persist and this suggestion is of last resort, one can manually enter dns values in /etc/resolv.conf and make this immutable by

Code: Select all

# chattr +i /etc/resolv.conf

Hope you do not have to resort to this.