if you put something in the dns you do so because you want to discovered. scoping the nameservers such that they only express certain certain resource records to queriers in a particular scope is fairly straight forward.
From: Joel Jaeggli <joelja@bogus.com>
What about privacy concerns
"Privacy is dead. Get used to it." -- Scott McNeely
Forget that attitude, Valdis. Just because privacy is blown at one level
doesn't mean you give it away at every other one. We establish the framework
for recovering privacy and make progress step by step, wherever we can.
Someday we'll get it all back under control.if you put something in the dns you do so because you want to discovered. scoping the nameservers such that they only express certain certain resource records to queriers in a particular scope is fairly straight forward.
--------------------------------------------------------The article was not about DNS. It was about "Persistent Personal Names for Globally Connected Mobile Devices" where "Users normally create personal names by introducing devices locally, on a common WiFi network for example. Once created, these names remain persistently bound to their targets as devices move. Personal names are intended to supplement and not replace global DNS names."
you mean like mac addresses? those have a tendency to follow you around in ipv6...
This is why RFC 3041 (replaced by 4941) was written, 10+ years ago. The problem
is that it's not enabled by default on many (possibly all) platforms, so I
have to have
# cat /etc/sysctl.conf
net.inet6.ip6.use_tempaddr=1
set on my Mac.
--Steve Bellovin, https://www.cs.columbia.edu/~smb