Or build your own private DNS zone infrastructure. If you need to do a
dynamic register to the DNS, you've got to have one anyway. Unless you're
trying to enforce DNSSEC there, this won't be a big hassle. Not depending on
the DNS is a viable solution, nevertheless.
Kenji Rikitake
++> Bob Ippolito <> [2014-02-17 09:04:22 -0800]:
> The best way to handle this is to force the nodes to come up with a
> predictable name, not dependent on reverse DNS, such as For
> discovery, these nodes can register themselves to some central directory
> (dynamic DNS, database, etc.) or send periodic broadcast messages (mDNS or
> some bespoke broadcast scheme).
>> On Monday, February 17, 2014, David Welton <> wrote:
>> > Hi,
> >
> > For various reasons, we sometimes have nodes that come up with a long
> > node name that does not nicely map onto the network - say,
> > or that does not get a
> > DNS entry. The nodes operate in somewhat unknown and unstable network
> > situation, so we may not even know the IP address ahead of time.
> >
> > It'd be nice to be able to - at a later date - force a connection to
> > those nodes by specifying an IP address in the connection code
> > somewhere.
> >
> > Is something like this at all feasible?
> >
> > Thank you