Bug#761658: Please do not default to using Google nameservers

[Marco d'Itri]

On Mar 29, Christoph Anton Mitterer <calestyo at scientia.net> wrote:

> And AFAIU the problem of data/privacy leakage isn't just made up, is it?
So far, it is. If you still want to argue about this (which I something
that I strongly recommend against!), then you should explain in detail 
the threat model that you are trying to address and how the current 
configuration would be worse than other configurations.

> $ geoiplookup 8.8.8.8
> GeoIP Country Edition: US, United States
traceroutes from multiple non-US locations may surprise you.

> Or are there already Code of Conflict cases running against me now or
> Marco because he used the word "lunacy" on someone else's work o.O
I argue that alternative DNS roots are firmly in the camp of net.kooks, 
and there is more than enough history to support this.
Were you around at the time of the newdom mailing list? Fun times...
Be careful of who you choose to associate with, because you will be 
judged by your peers for it.

> > Marco told you specifically, how you can configure this explicitly.
> Uhm? I just accidentally stumbled over this bug and I don't think he has
> told me anything in specific.
I did, in my reply. Short summary: have a resolv.conf file or use DHCP.

> IMO, OpenNIC or anything else would have the same issues than Google:
Then maybe you should work in the IETF to establish either:
- well know IP addresses which will provide recursive DNS service (this 
  may even work now that we have DNSSEC)
- a best practice of running a caching resolver on every end user system 
  (I highly doubt that this would be considered a good idea)

-- 
ciao,
Marco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 648 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150329/7ce8ee75/attachment-0002.sig>