Can the KACE agent communication with the K1000 using a different DNS name to the web server FQDN?


We don't have the K1000 facing the internet and have it behind a WAF for the Helpdesk.

Having some fun with VPN and DNS resolution so I'm just wondering if we can configure the Agent with a DNS address for the K1000 that is different to the configure FQDN?

The reason I ask is I have tried but think I'm seeing the Agent reconfigure itself back to the FQDN.

Should the Agent just obey what it is configured with?



0 Comments   [ + ] Show comments

Answers (1)

Posted by: Nico_K 2 years ago
Red Belt

The agent config file is always rewritten with the webserver name, since the webserver name is the name where it tries to up- and downloads.
If the config file would keep its "original config" a connection would fail usually.
You can modify your DNS settings in the env to allow a correct communication. 

There is a plan to ease some settings for special environments in the future (which would make my current workaround for internal DNS to the internal IP of the appliance no more nessesary) but not 100% clear which version will bring this improvement.

  • "You can modify your DNS settings in the env to allow a correct communication. "

    Can you clarify what you mean with this comment? - theatrebyte 2 years ago
    • you can set an A (or AAAA) record for the alternative DNS name you need (or forwarding or similar, really depending on your env or even hardcode the IP in the hosts-file on the clients if you like) - Nico_K 2 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ