$Id$

           mynode
   +-+       +-+
   | |       | |----|
   +-+       +-+    |- mywww._http._tcp.local (SRV record?)
      \     /       |
       \   /        |- 192.168.1.19 by name ______ (A record)
        +-+        -|          ___________
        | |         |         /           \
        +-+         |  +--+  /             \     +------------+
                    |--|gw|-|  Internet     |----| dns server |
                       +--+  \             /     +------------+
                              \___________/\
                                            \
                                             \
                                              +--------------+
                                              | ddns server  |
                                              +--------------+

name filters:

  from lan to internet:

        pass myftp._ftp._tcp.local
        stop private-www._http._tcp.local
        pass *._http._tcp.local
        stop *

  from internet to lan:

        pass ftp._ftp._tcp.friendsnode.friendsdomain

name transformations:

        translate *._http._tcp.local to *._http._tcp.mynode.mydomain
        translate mywww._http._tcp.local to www._http._tcp.mynode.mydomain
        call 192.168.1.19 by myserver.mynode.mydomain

In addition to the nat, natr, and 6to4 link properties advertised
by HSLS for purposes of gateway discovery, there will be link
properties ns and nsd, indicating name service and dynamic name
service---i.e., a server where routers can register new name<->number
associations.  See dyndns.org.

Record type     Key             Value

dns-server      server-ip       [domain-name]
ddns-server     server-ip       domain-name, needs-auth
search          domain-name

$Id$