Re: DNS Expectations (was rtsol)

[christos%astron.com@localhost (Christos Zoulas)]

In article <5446A40D.4010301%marples.name@localhost>,
Roy Marples  <roy%marples.name@localhost> wrote:
>On 21/10/2014 17:47, Robert Swindells wrote:
>> But dhcpcd has not learned the information that is being deleted.
>> 
>> I am suggesting that in the case where nothing is returned then no
>> change should be made to resolv.conf.
>
>These are indeed fair points, but I feel the conversion has now moved
>from dhcpcd(8) to resolvconf(8).
>
>resolvconf(8) simply takes all available inputs and then outputs
>something sensible. Without any configuration or input you get a blank
>resolv.conf(5).
>
>Of course, we could do things a little differently. Here's some ideas,
>from worst to best in my mind:
>
>  *  resolvconf should be opt-in rather than opt-out in resolvconf.conf
>
>  *  refuse to update resolv.conf if it doesn't contain the resolvconf
>     signature when adding or removing interfaces via resolvconf
>
>  *  if resolv.conf has no valid signature, save it and only restore it
>     when resolvconf has no valid inputs left
>
>Any of these changes could affect the long standing behaviour of
>resolvconf placing a blank resolv.conf file to make 127.0.0.1 the
>resolver to use.

I just want to be able to precisely control its behaviour which in the
current configuration language I cannot. I.e. I should be able by setting
variables to affect the output resolv.conf file to be exactly how I
like it. For example, if I want 127.0.0.1 not to be the first resolving
nameserver, I should be able to do it. If I want to change the domain,
I should be able to do it. If I want to delete the ISP's nameservers
and the ISP suffix from the search path, I should be able to do it.
Right now resolvconf does what it thinks is better, and gets it wrong.

It is simple to fix this: For each variable provide a prepend, append,
and replace variable override, like dhclient does.

christos