2 Replies Latest reply on Mar 19, 2008 12:34 PM by carlilek

    Agent Configuration

    Rookie

       

      Hi,

       

       

      If I am using a Management Gateway I presume that I need to use a fully qualified domain name for the core server, and use split DNS for the internal and external clients to resolve this?

       

       

      E.g. 'ldms.company.com' resolves on the internal network to the core server IP address, and on public DNS to the management gateway external IP address.

       

       

      Does it matter if the  dns name does not match the actual server name, e.g. dns name 'ldms.company.com', server name actually 'ldcore'

       

       

      Thanks,

      Paul

       

       

        • 1. Re: Agent Configuration
          pk Employee

           

          It's actually crucial that the FQDN for the core is not resolvable out in Internet-land as this is one of the first checks LANDesk does to determine if the core is reachable or not.  So your core and gateway should have their own unique names.

           

           

          It is possible that having an alias for your core will effect connectivity through the gateway.  The core name is baked into the cert that is passed and if these are mismatched it can cause the connection to fail.  So, the simplest approach is to use one name for your core.

           

           

          • 2. Re: Agent Configuration
            Apprentice

            And don't change the ip address or the fqdn on the core after it's built. Otherwise you're going to be rebuilding it.