On 12/16/2014 12:06 PM, Saul Wold wrote:
> On 12/16/2014 08:55 AM, Philip Balister wrote:
>> On 12/16/2014 11:40 AM, Khem Raj wrote:
>>>
On Dec 16, 2014, at 7:12 AM, Philip Balister
wrote:
Any tips on how to do this the right way? It seems like fixed
resolv.conf's are no l
On 12/16/2014 08:55 AM, Philip Balister wrote:
On 12/16/2014 11:40 AM, Khem Raj wrote:
On Dec 16, 2014, at 7:12 AM, Philip Balister wrote:
Any tips on how to do this the right way? It seems like fixed
resolv.conf's are no longer fashionable and the volatile.cache script
goes to great lengths
On 12/16/2014 11:40 AM, Khem Raj wrote:
>
>> On Dec 16, 2014, at 7:12 AM, Philip Balister wrote:
>>
>> Any tips on how to do this the right way? It seems like fixed
>> resolv.conf's are no longer fashionable and the volatile.cache script
>> goes to great lengths to reset it.
>>
>> Adding a dns-na
> On Dec 16, 2014, at 7:12 AM, Philip Balister wrote:
>
> Any tips on how to do this the right way? It seems like fixed
> resolv.conf's are no longer fashionable and the volatile.cache script
> goes to great lengths to reset it.
>
> Adding a dns-nameserver entry in the interfaces file never mak
Any tips on how to do this the right way? It seems like fixed
resolv.conf's are no longer fashionable and the volatile.cache script
goes to great lengths to reset it.
Adding a dns-nameserver entry in the interfaces file never makes it to
resolv.conf. I tried installing the resolvconf package and p
