First check if the IP address is not within the list of endpoints for OA by running oneagentctl --get-server
If this is the case, then most likely the IP address comes from one of your ActiveGates which you can confirm in Deployment status.
Hello, it is an on-premise environment, the ip you mention is within the environment that raise the kubernets in Rancher, apparently the agents do not see as first option and try to connect through the other interface, is there any way I can define the ip addressing that raises or if this is corrected by assigning a network zone
Hey @juanrergis ,
Sure it's possible by defining the dnsEntryPoint for the ActiveGate in custom.properties. If it's a containerized ActiveGate in Kubernetes, then you need to specify that in the DynaKube resource as shown here.