[erlang-questions] random thought: connecting to node, specify IP address

David Goehrig dave@REDACTED
Wed Feb 19 15:46:58 CET 2014

I do just this...


For apps like RabbitMQ and Riak I use a FQDN based on the internal TLD.  Works well and assuming you set your domain search in /etc/resolv.conf in your base image, cloud-init supplied hostnames just work. 


-=-=- dave@REDACTED -=-=-

> On Feb 18, 2014, at 6:26 AM, Kenji Rikitake <kenji@REDACTED> wrote:
> 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 <bob@REDACTED> [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 foo@REDACTED 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 <davidnwelton@REDACTED> 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,
>>> foo@REDACTED or foo@REDACTED 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
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

More information about the erlang-questions mailing list