You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that DNS servers in /etc/resolv.conf are set to some weird settings after each reboot, as follows:
nameserver 192.168.0.1
nameserver 8.8.4.4
nameserver 8.8.8.8
nameserver 114.114.114.114
nameserver 119.29.29.29
nameserver 223.5.5.5
(first is some 'local/private' IP but not from my local subnet, two next servers are Google's, the last three are unknown to me),
None of these servers would work in my case because my IoT network segment is only allowed to send DNS requests to my internal DNS servers, in my local/private subnet.
If /etc/resolv.conf is changed manually, it works fine then but it restores itself to incorrect values after every device reboot. Same about changing /boot/resolv.conf.
I found a wrokaround in another issue report (modify /etc/resolv.conf and then set immutable flag on it with chattr) and then it works as expected (changes to /etc/resolv.conf survive reboot). But it is really not as it should work.
The text was updated successfully, but these errors were encountered:
I found that NanoKVM DHCP client creates /etc/resolv.conf.dhcp with proper DNS server and domain suffix, obtained from DHCP server. But this left unused, unless copied or symlinked to /etc/resolv.conf.
So, after some experiments, and using your workaround, I created /etc/init.d/S99resolv-fix:
It starts as service during reboot.
Sure, it's quite crude and optimistic solution, but it works.
However, I can't predict what consequences this will lead to. Probably, the default settings were made as is for some purposes, not just for fun.
Hi,
I have IP address/gateway set statically.
I noticed that DNS servers in /etc/resolv.conf are set to some weird settings after each reboot, as follows:
nameserver 192.168.0.1
nameserver 8.8.4.4
nameserver 8.8.8.8
nameserver 114.114.114.114
nameserver 119.29.29.29
nameserver 223.5.5.5
(first is some 'local/private' IP but not from my local subnet, two next servers are Google's, the last three are unknown to me),
None of these servers would work in my case because my IoT network segment is only allowed to send DNS requests to my internal DNS servers, in my local/private subnet.
If /etc/resolv.conf is changed manually, it works fine then but it restores itself to incorrect values after every device reboot. Same about changing /boot/resolv.conf.
I found a wrokaround in another issue report (modify /etc/resolv.conf and then set immutable flag on it with chattr) and then it works as expected (changes to /etc/resolv.conf survive reboot). But it is really not as it should work.
The text was updated successfully, but these errors were encountered: