openresolv-discuss

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'

-------  8<    ------------------------

root@RPI01-01:/etc# cat resolvconf.conf
# Configuration for resolvconf(8)
# See resolvconf.conf(5) for details

resolv_conf=/etc/resolv.conf
# If you run a local name server, you should uncomment the below line and
# configure your subscribers configuration files below.
#name_servers=127.0.0.1
name_servers=192.168.10.1

# Mirror the Debian package defaults for the below resolvers
# so that resolvconf integrates seemlessly.
dnsmasq_resolv=/var/run/dnsmasq/resolv.conf
pdnsd_conf=/etc/pdnsd.conf
unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf

-------  8<    ------------------------

root@RPI01-01:/var/lib/dhcp# cat dhclient.leases
lease {
  interface "enxb827eb2a22d7";
  fixed-address 192.168.10.103;
  option subnet-mask 255.255.255.0;
  option routers 192.168.10.1;
  option dhcp-lease-time 86400;
  option dhcp-message-type 5;
  option domain-name-servers 192.168.10.1,92.220.228.70,109.247.114.4;
  option dhcp-server-identifier 192.168.10.1;
  option dhcp-renewal-time 43200;
  option broadcast-address 192.168.10.255;
  option dhcp-rebinding-time 75600;
  option host-name "RPI01-01";
  option domain-name "home";
  renew 6 2018/02/10 08:21:58;
  rebind 6 2018/02/10 19:54:40;
  expire 6 2018/02/10 22:54:40;
}



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

> On 10/02/2018 07:36, Tarjei Jensen wrote:
>
>> Thanks for the suggestion. I may have to do that.
>>
>> The dhclient.leases file indicates that 192.168.10.1 is first in the list
>> of DNS servers. And there is only one lease.
>>
>>   option domain-name-servers 192.168.10.1,92.220.228.70,109.247.114.4;
>>
>> I notice that the name servers in /etc/resolv.conf are listed in
>> numerical order. However, I found no sort in /sbin/resolvconf or in
>> /sbin/dhclient-script.
>>
>
> There is infact sorting, but not inside one lease.
> What is the output of
>
> resolvconf -l and resolvconf -v
>
> ?
>
> Also, could you consider upgrading to openresolv-3.9.0?
> While there's no specific fix there which would address this issue, it
> doesn't hurt either.
>
> I also notice that the name resolver assumes that all DNS servers have the
>> same information. It stops trying to resolve names at the first server that
>> works. That is not the way I would have designed it.
>>
>
> That's outside the scope of openresolv and what it does.
>
> Roy
>