Re: resolv.conf.head

2015-01-09 Thread Jason Adams
On 01/09/2015 12:49 PM, mar...@martinbrandenburg.com wrote: > And you realize that your ISP (like Comcast or Verizon) can see your DNS > queries even if you point them at another nameserver. Granted I've met enough > ISP nameservers which return advertising instead of NXDOMAIN, and that is > annoy

Re: resolv.conf.head

2015-01-09 Thread martin
wise sending all of our DNS queries to lovely companies like > Comcast and Verizon. > > Nameserver overrides be done with dhclient.conf, but it seems more clear > and Unixy to just have a resolv.conf.head counterpart to > resolv.conf.tail. It already exists in a certain other Unix-lik

Re: resolv.conf.head

2015-01-09 Thread Alexander Hall
onf, it will supersede anything you include in >>resolv.conf.tail. >>Wanting to specify the nameserver is common, because many of us are >>otherwise sending all of our DNS queries to lovely companies like >>Comcast and Verizon. >> >>Nameserver overrides be done with dhc

Re: resolv.conf.head

2015-01-09 Thread Alexander Hall
mon, because many of us are >otherwise sending all of our DNS queries to lovely companies like >Comcast and Verizon. > >Nameserver overrides be done with dhclient.conf, but it seems more >clear >and Unixy to just have a resolv.conf.head counterpart to >resolv.conf.tail. It alread

resolv.conf.head

2015-01-09 Thread Libertas
and Verizon. Nameserver overrides be done with dhclient.conf, but it seems more clear and Unixy to just have a resolv.conf.head counterpart to resolv.conf.tail. It already exists in a certain other Unix-like operating system of great popularity. Is this a good idea? If so, I can try writing a patch.