[erlang-bugs] Erlang doesn't connect with "short" long names
Lukas Larsson
lukas@REDACTED
Fri Jul 29 12:31:33 CEST 2011
Hello!
If you feel like something is missing to the documentation, please take
the time to add it and submit a patch so that it will be clearer to
others how Erlang/OTP works.
The source for the documentation in question can be found here:
https://github.com/erlang/otp/blob/dev/erts/doc/src/epmd.xml
Lukas
On 29/07/11 12:14, Vincenzo Maggio wrote:
> Hi,
> you are perfectly right, nslookup reckons mydomain.com (what a bad
> luck, I didn't think that someone could register "mydomain.com"!) but
> not b.c.
> What misled me is the fact that I thought that being on the same host,
> the epmd deamon could manage to ping the nodes because I added them to
> hosts file.
> Indeed, when you issue 'epmd -nodes' it recognizes the nodes names
> (like 'a' and 'b') without the host and domain part, so I thought that
> epmd simply uses a simple host lookup, not a domain lookup.
> I think that it should be pointed out in erlang docs that epmd uses
> nslookup to route requests between nodes.
> As far as you know, is this the right place for this kind of suggestions?
>
> Many thanks for the help!!!
>
> Vincent
>
> > Date: Fri, 29 Jul 2011 09:02:56 +0200
> > From: ess@REDACTED
> > To: maggio.vincenzo@REDACTED
> > CC: erlang-bugs@REDACTED
> > Subject: Re: [erlang-bugs] Erlang doesn't connect with "short" long
> names
> >
> > Shinji Ikari wrote:
> > > Hello,
> > > the problem, on my laptop (Win XP SP3, OTP/R14B3), can be simply
> > > replicated with starting two nodes with "short" long names and try to
> > > connect them:
> > >
> > > c:\> erl -name a@REDACTED
> > > (a@REDACTED)1>
> > >
> > > and
> > Does the host in question in fact have the name 'a.b.c'?
> > I.e. if you run "nslookup a.b.c", do you get the IP of the machine on
> > which you're starting that node?
> > Otherwise, what you try is not expected to work.
> > >
> > > c:\> erl -name b@REDACTED
> > > (b@REDACTED)1>net_adm:ping(a@REDACTED).
> > > pang
> > > (b@REDACTED)2>nodes().
> > > [] -----> as expected after a 'pang'!
> > >
> > > So Erlang doesn't seem to connect this way. But if you simply:
> > >
> > > c:\> erl -name a@REDACTED
> > > (a@REDACTED)1>
> > >
> > > c:\> erl -name b@REDACTED
> > > (b@REDACTED)1>net_adm:ping(a@REDACTED).
> > > pong
> > > (b@REDACTED)1>nodes().
> > > [a@REDACTED] -----------> as expected after a 'pong'!
> > >
> > >
> > > Really, no clue here, I've also checked standard rules for domain
> > > names: there is an upper limit (63 characters) but no lower limit,
> AFAIK.
> > >
> > > Thanks in advance!
> > >
> > > Vincent
> >
>
>
> _______________________________________________
> erlang-bugs mailing list
> erlang-bugs@REDACTED
> http://erlang.org/mailman/listinfo/erlang-bugs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-bugs/attachments/20110729/a38e59a1/attachment.htm>
More information about the erlang-bugs
mailing list