[dns-operations] [Ext] How should work name resolution on a modern system?
phill at hallambaker.com
Thu Jun 16 02:08:26 UTC 2022
It is my firm belief that the collapse of the crypto-ponzi world and the
$45 name coins is an essential precondition for anything useful to happen
in this space. It is possibly fortuitous that this appears to be underway
as we speak.
One reason we are where we are is that UNIX doesn't actually have a DNS
interface, it has a name service API that predates DNS which has been
repurposed. So very little of the power of DNS is actually visible to the
application. Unless you write your own DNS resolution API and that has
Use of .local is a kludge.
Proposing something better is easy. Been there, done that, have running
code. Deployment is the hard part.
On Wed, Jun 15, 2022 at 7:52 PM Viktor Dukhovni <ietf-dane at dukhovni.org>
> On Wed, Jun 15, 2022 at 07:13:30PM -0400, Phillip Hallam-Baker wrote:
> > I am of course fully aware of the commercial and technical issues that
> > it very difficult for the incumbents to address this problem. But that
> > doesn't change the fact that a system designed to meet the needs of
> > educational institutions exchanging email in the 1980s is really not fit
> > for purpose for the needs of five billion users in the 2020s.
> Less stridently, we can recognise that the service discovery APIs we
> have do not have a first-class notion of overlay "views" each with its
> own independent naming tree, and the applications running on top of
> these APIs don't have syntax for choosing a view in which to resolve
> such names.
> The closest we have is the ".local" subspace of the global DNS, and
> reaching IETF consensus on such special use namespaces has been
> exceedingly complex.
> So the DNS is fundamentally a *global* namespace, but one in which
> businesses often overlay a single additional internal view.
> I don't think this is so much a *DNS* problem as such, or that DNS is
> not fit for purpose, but I do agree that requirements are shifting,
> and that indeed home automation is served poorly by a global namespace,
> and an overly centralised operational model.
> Sadly, time to market seems to favour doing what already works, however
> poorly. I do hope that real innovation can happen in this space, and
> better solutions found. It won't be easy.
> dns-operations mailing list
> dns-operations at lists.dns-oarc.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dns-operations