Hi,
Thanks for the question. If I understand it properly, the use case you
consider: 1) you set up a web server in your homenet, 2) you want it to be
accessed from the outside so you register your domain name and register the
IP address to the zone. Note that In this case, the Authoritative
Thanks for your answer, Daniel.
If I understand it properly, the use case you consider: 1) you set up
a web server in your homenet, 2) you want it to be accessed from the
outside so you register your domain name and register the IP address to
the zone. Note that In this case, the
I'd like to understand why the device needs to go through the middleman
rather than speaking directly to the authoritative DNS server.
You may find some useful background in RFC 5625.
I'm increasingly confused. RFC 5625 is about proxying DNS requests from
the LAN. Daniel's draft is about
On Thu, Jul 03, 2014 at 02:39:26PM +0200, Juliusz Chroboczek wrote:
I'm increasingly confused. RFC 5625 is about proxying DNS requests from
the LAN. Daniel's draft is about proxying dynamic DNS updates, right?
Yes. My impression is that the idea in Daniel's draft is that the ISP
will take
On Thu, 3 Jul 2014, Douglas Otis wrote:
Since mDNS is unable to make determinations regarding the ability of a
device to safely interact with the Internet, an overlay approach could
be taken. Although details are missing from the Hybrid
Unicast/Multicast DNS-Based Service Discovery draft,
