Results 1 to 9 of 9

Thread: ICE without DNS Server

  1. #1
    wgwolf is offline Registered User
    Name: Wolfgang
    Organization: Uni Erlangen - Germany
    Project: .
    Join Date
    Oct 2005
    Location
    Nuremberg, Germany
    Posts
    10

    ICE without DNS Server

    Hi,

    we have a tiny own linux distribution without any DNS Server realized. We just operate with IP addresses.
    This is a problem for an ICE server as it seems to be that it wants to resolve the local hostname to its IP address.
    The error message is:
    DNSException: exception ::Ice:NSException
    {
    error = -5
    host = entity_4
    }

    Is there any possibility to run ICE without any DNS functionality?

    Thanks!
    Wolfgang

  2. #2
    marc's Avatar
    marc is offline ZeroC Staff
    Name: Marc Laukien
    Organization: ZeroC, Inc.
    Project: The Internet Communications Engine
    Join Date
    Feb 2003
    Location
    Florida
    Posts
    1,860
    Please see this thread regarding our support policy here on these forums:

    http://www.zeroc.com/vbulletin/showthread.php?t=1697

  3. #3
    wgwolf is offline Registered User
    Name: Wolfgang
    Organization: Uni Erlangen - Germany
    Project: .
    Join Date
    Oct 2005
    Location
    Nuremberg, Germany
    Posts
    10
    Signature and profile is set.
    Thank you for your help.
    Wolfgang


    Quote Originally Posted by marc
    Please see this thread regarding our support policy here on these forums:

    http://www.zeroc.com/vbulletin/showthread.php?t=1697

  4. #4
    marc's Avatar
    marc is offline ZeroC Staff
    Name: Marc Laukien
    Organization: ZeroC, Inc.
    Project: The Internet Communications Engine
    Join Date
    Feb 2003
    Location
    Florida
    Posts
    1,860
    Is this with Ice for C++? Do you get the problem also if you explicitly set the -h option for your endpoint? You can also try to set Ice.Default.Host.

  5. #5
    wgwolf is offline Registered User
    Name: Wolfgang
    Organization: Uni Erlangen - Germany
    Project: .
    Join Date
    Oct 2005
    Location
    Nuremberg, Germany
    Posts
    10
    It is Ice for Python. But the -h option doesn't seem to take any effect in the following line:
    adapter = self.communicator().createObjectAdapterWithEndpoin ts("Machine", "default -h Ice.Default.Host -p 10000")
    Independent of what is set up with -h, neither any hostname nor an ip address, ice only wants always to resolve the name of the local machine.

    Wolfgang


    Quote Originally Posted by marc
    Is this with Ice for C++? Do you get the problem also if you explicitly set the -h option for your endpoint? You can also try to set Ice.Default.Host.
    University of Erlangen-Nuremberg
    Institute for Manufacturing Automation and Production Systems
    Egerlandstr. 7-9
    D-91058 Erlangen
    Germany
    URL: www.faps.uni-erlangen.de

  6. #6
    benoit's Avatar
    benoit is online now ZeroC Staff
    Name: Benoit Foucher
    Organization: ZeroC, Inc.
    Project: Ice
    Join Date
    Feb 2003
    Location
    Rennes, France
    Posts
    2,196
    Ice.Default.Host is a configuration property (see the manual for more information). You should try to set it with the IP address of your machine and not specify the -h option in the endpoints of your object adapters (they will use the default set in Ice.Default.Host).

    For example, with the IcePy hello demo, you can use the following to make sure it will use 192.168.0.3 as the default host:

    $ python Server.py --Ice.Default.Host=192.168.0.3 --Ice.Trace.Network

    Can you try this? Also, if you have the stack trace of the exception, it would be helpful to include it, this might give some hints...

    Benoit.

  7. #7
    wgwolf is offline Registered User
    Name: Wolfgang
    Organization: Uni Erlangen - Germany
    Project: .
    Join Date
    Oct 2005
    Location
    Nuremberg, Germany
    Posts
    10
    It works fine! Thank you!
    Another question: how can I bind the server to several ip addresses?
    with Ice.Default.Host you can just set one ip address.

    Wolfgang


    Quote Originally Posted by benoit
    Ice.Default.Host is a configuration property (see the manual for more information). You should try to set it with the IP address of your machine and not specify the -h option in the endpoints of your object adapters (they will use the default set in Ice.Default.Host).

    For example, with the IcePy hello demo, you can use the following to make sure it will use 192.168.0.3 as the default host:

    $ python Server.py --Ice.Default.Host=192.168.0.3 --Ice.Trace.Network

    Can you try this? Also, if you have the stack trace of the exception, it would be helpful to include it, this might give some hints...

    Benoit.
    University of Erlangen-Nuremberg
    Institute for Manufacturing Automation and Production Systems
    Egerlandstr. 7-9
    D-91058 Erlangen
    Germany
    URL: www.faps.uni-erlangen.de

  8. #8
    benoit's Avatar
    benoit is online now ZeroC Staff
    Name: Benoit Foucher
    Organization: ZeroC, Inc.
    Project: Ice
    Join Date
    Feb 2003
    Location
    Rennes, France
    Posts
    2,196
    Yes, it's not the purpose of the Ice.Default.Host property to define the endpoints of object adapters (and therefore the interfaces the object adapter will listen to). See the description of this property in the Appendix C.7 of the Ice manual for more information.

    If you use the createObjectAdapterWithEndpoints method to create the object adapter, you have to specify the object adapter endpoints directly in the code, for example:

    Code:
       Ice::ObjectAdapterPtr adapter = communicator->createObjectAdapterWithEndpoints("Machine", "tcp -p 10000 -h 192.168.0.3:tcp -p 10000 -h 1.1.0.3");
    If you create the object adapter with the createObjectAdapter method, you can set the endpoints with configuration properties. For example, if you create the adapter with the following code:

    Code:
       Ice::ObjectAdapterPtr adapter = communicator->createObjectAdapter("Machine");
    You can set the object adapter endpoints with the Machine.Endpoints property in a configuration file, for example:
    Code:
      Machine.Endpoints=tcp -p 10000 -h 192.168.0.3:tcp -p 10000 -h 1.1.0.3
    You can turn on the network tracing (--Ice.Trace.Network=1) to make sure your server will listen on the endpoints specified either in the code or the configuration.

    Benoit.

  9. #9
    dwayne's Avatar
    dwayne is offline ZeroC Staff
    Name: Dwayne Boone
    Organization: ZeroC, Inc.
    Project: Internet Communications Engine
    Join Date
    Jan 2005
    Location
    St. John's, Newfoundland
    Posts
    397
    Just a note that in the next release of Ice if you do not specify a -h parameter in the endpoint configuration and Ice.Default.Host is not set then Ice will listen on all local interfaces.

    Regards,
    Dwayne

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. DNS cache
    By alexnycheung in forum Help Center
    Replies: 1
    Last Post: 12-08-2009, 07:04 AM
  2. Connection establishment and DNS
    By sportlane in forum Help Center
    Replies: 4
    Last Post: 07-20-2009, 09:12 AM
  3. ICE SSL binding to DNS hostname
    By dhogan in forum Help Center
    Replies: 5
    Last Post: 02-12-2008, 12:54 PM
  4. dns exception
    By timberwolf in forum Help Center
    Replies: 3
    Last Post: 06-26-2007, 02:09 AM
  5. can we use dns name as Endpoint's host name?
    By xiehua in forum Help Center
    Replies: 1
    Last Post: 02-18-2004, 07:34 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •