[erlang-questions] Distributed erlang problem

Hal Snyder drxyzzy@REDACTED
Wed Mar 19 16:41:32 CET 2008

Understood, that ops & policy enter into the solution. I suspect a  
more natural solution might be to alias a loopback interface on the  
db hosts and use routing rules to make sure OMC and db hosts find one  
another over the correct interfaces. You could use DNS if other apps  
on db hosts are ok with the aliased loopback (that would be more  
consistent), or else launch db nodes using the aliased IP addresses  
in their node names.

On Mar 19, 2008, at 8:59 AM, Chandru wrote:

> On 19/01/2008, Serge Aleynikov <saleyn@REDACTED> wrote:
> Chandru wrote:
> > Well - there is an issue. This is because on the OMC node, host1- 
> rep is
> > resolving to an IP address to which routing doesn't exist from  
> the OMC (and
> > I can't get it added). The Security team won't allow this  
> connectivity.
> >
> It sounds like what you need is to resolve a host name to IP on OMC  
> that
>   doesn't resolve using default resolution method.
> What you can do is specify the {kernel, [{inetrc, CustomConfigFile}]}
> option that will customize the name resolution search path used by
> distributed Erlang.
> I had suggested something similar to our Ops team. I asked them to  
> modify /etc/hosts and customise the name resolution there which  
> they aren't very happy about. I like your suggestion - it only  
> impacts the erlang nodes and won't affect any other services on the  
> server.
> ta
> Chandru

More information about the erlang-questions mailing list