Re: [dnssd] Example Use Cases (was Re: Rechartering)

[Ted Lemon <[e-mail]>]

ISTM means "It seems to me."

I think a global-scope FQDN for the local network that includes the
corporation's domain name is quite unlikely, but it's easy to imagine that
if it were *useful*, an ISP or a third party might offer it as a service
(as with dyndns.org, but delegating a zone rather than just allowing a name
to be updated).  The benefit for this is simply external reachability of
services, so it may be that a better solution would just be a DoH tunnel or
VPN tunnel that you could access with the right credentials that would
allow you to query home.arpa.   It would be nice if this sort of thing
could be more automatic, with less user IT fu required.

On Mon, Jul 23, 2018 at 11:11 AM, R. Atkinson <[e-mail]> wrote:

> From what I am seeing, I think the big barrier to local server deployment
> is the knowledge required to correctly deploy a local server.  This is a
> big
> issue whether its a DNS server or some other kind of server (e.g.
> SMTP/POP).
>
> Some company could make good money by creating an IT server that
> is MUCH MUCH easier to deploy, configure, and update/maintain.
>

We've seen devices like this—they just aren't typical.   Your printer is
like this.   If you have an Apple Time Machine or Homekit, it's like this.
 Making devices findable in this way isn't that hard, and enrollment really
isn't that hard either.   The issue is that right now for most use cases
nobody's making devices that work this way.   I think that's the barrier to
adoption.   I don't think that the level of knowledge in the deployment
environment is going to up.   I hope that the level of knowledge required
to deploy will go down.