Op woensdag 13 april 2016 16:35:39 CEST schreef sdm:
On 04/13/2016 04:29 PM, gumb wrote:
I wonder if, with all the updates to Leap, a new install + updates now would generate the same issue.
The resolv.conf file didn't contain the right details and entering them in YaST fails to insert them, even though I'd added name servers and the default IPv4 gateway within the Network Settings dialogs. No routes file is generated in /etc/sysconfig/network. I supposed at the time that Wicked used some other configuration and these details weren't necessary.
This is Tumbleweed, latest snapshot, just for the record. If I entered a name server in YaST2 Network Settings on the Hostname/DNS tab and it wrote that somewhere else, DNS won't work properly until I add the name server to /etc/resolv.conf. So either I'm doing something wrong and missing something or its an issue with Yast2 and/or Wicked.
Did you read the lines about editing /etc/resolv.conf, they're in the file. Years ago I missed reading those lines which threw me in a situation like you describe. If I suspect /etc/resolv.conf not to be correct, I remove it, restart the networkservice so that it will be regenerated. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org