Hi, Joachim,
Apologies, I could only answer just now. The problem is, for sure,
that restarting the Network Manager did not create the "nameserver
192.168.100.1" entry in /etc/resolv.conf. This is the entry which is
solely responsible for DNS name resolving, and its omission deprives
you from getting an answer to your ping request you mentioned.
I am unsure as to what is the exact reason.
I would suggest the following three actions, to further try to
understand the issue:
1) post here the content of /etc/NetworkManager/NetworkManager.conf
2) if this config file has "dns=dnsmasq" entry, try to comment it and
restart NetworkManager, then see if /etc/resolv.conf is empty or not.
3) tell us if selinux is enabled on this machine (the output of
"getenforce" from the command line)
Regards,
Rami Rosen
http://ramirose.wix.com/ramirosen
On 6 July 2016 at 17:29, Joachim Backes <joachim.backes(a)rhrk.uni-kl.de> wrote:
> On 07/06/16 15:54, Rami Rosen wrote:
>> Hi, Joachim,
>>
>> Regarding DNS resolving: the /etc/resolv.conf, which is generated by
>> Network Manager, as responsible for DNS resolving
>> Can you please post the output of
>> cat /etc/reslov.conf
>> after fresh reboot, before restarting NetworkManager, when
>> ping <hostname> succeeds,
>> and after restargin NetworkManager, when
>> "ping: <hostname> fails ?
>
> Hi Rami,
>
> /etc/resolv.conf before NM restart
> ----------------------------------
> # Generated by NetworkManager
> nameserver 192.168.100.1
>
> /etc/resolv.conf after NM restart
> ----------------------------------
> # Generated by NetworkManager
>
> journalctl -f before and after NM restart: See attached file
"journalctl-f"
> (the dashed line in "journalctl-f" marks the restart)
>
>
> Kind regards
>
> Joachim Backes
>
>
>
> --
>
> Fedora release 24 (Twenty Four)
> Kernel-4.6.3-300.fc24.x86_64
>
>
> Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
>
http://www-user.rhrk.uni-kl.de/~backes/