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-like
operating system of great popularity
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.
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 dhclient.conf, but it seems more
clear
and Unixy to just have a resolv.conf.head counterpart to
resolv.conf.tail. It already
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
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-like
operating system of great popularity.
Is this a good idea
5 matches
Mail list logo