openresolv-discuss

IT is working as expected.

I think there is both dhclient and dhcpcd involved. Unless dhcpcd creates a
dhclient.leases file in /var/lib/dhcp and reads the config from
/etc/dhcp/dhclient.conf That could explain the weirdness in the resolv.conf
file.

Greetings,



On Sat, Feb 10, 2018 at 1:52 PM, Roy Marples <roy@xxxxxxxxxxxx> wrote:

> On 10/02/2018 12:26, Tarjei Jensen wrote:
>
>> Hi,
>>
>> Before I changed resolvconf.conf, I rebooted and then resolv.conf did not
>> have the 192.168.10.1 server in it.
>>
>> I presumed that somehow it got clobbered by the duplicate removal. But
>> since I decided to add the server to the conf file instead of chasing that
>> problem.
>>
>> Greetings,
>>
>>
>> root@RPI01-01:~# resolvconf -l
>> # resolv.conf from enxb827eb2a22d7.dhcp
>> # Generated by dhcpcd from enxb827eb2a22d7.dhcp
>> domain home
>> search home
>> nameserver 92.220.228.70
>> nameserver 109.247.114.4
>>
>>
>> root@RPI01-01:~# resolvconf -v
>> DOMAIN='home'
>> SEARCH='home'
>> NAMESERVERS='192.168.10.1 92.220.228.70 109.247.114.4'
>> LOCALNAMESERVERS=''
>> DOMAINS='home:92.220.228.70,109.247.114.4'
>>
>
> So that shows that you're using dhcpcd and not dhclient which is why this
> happened.
>
> Is it now working as expected?
> It's not clear from your reply.
>
> Roy
>