[KEDA][Kafka] DNS resolution not working with a custom DNS server

This issue is a: (mark with an x)

• [ x] bug report -> please search issues before submitting
• documentation issue or request
• regression (a behavior that used to work and stopped in a new release)

Issue description

We use custom kafka KEDA rule on a pod, but the dns resolution doesn't work as expected.
Our Kafka cluster is linked to a private endpoint.
So the dns resolution inside a pod is
xxxx.westeurope.azure.confluent.cloud => X.240.Y.Z
and from KEDA
xxxx.westeurope.azure.confluent.cloud =>10.1.0.4

our scaling rule :

"scale": {
    "minReplicas": 1,
    "maxReplicas": 6,
    "rules": [
        {
            "name": "kafka-rule",
            "custom": {
                "type": "kafka",
                "metadata": {
                    "bootstrapServers": "xxxx.westeurope.azure.confluent.cloud:9092",
                    "consumerGroup": "myconsumergroup",
                    "lagThreshold": "20",
                    "offsetResetPolicy": "earliest",
                    "sasl": "plaintext",
                    "tls": "enable",
                    "topic": "mytopic"
                },
                "auth": [
                    {
                        "secretRef": "kafka-keda-username",
                        "triggerParameter": "username"
                    },
                    {
                        "secretRef": "kafka-keda-password",
                        "triggerParameter": "password"
                    }
                ]
            }
        }
    ]
},

note that the kafka cluster url has a public resolution => 10.1.0.4, but in our network is X.240.Y.Z.

Steps to reproduce

1. use confluent KAfka cluster with private connectivity
2. create Azure VNET and set DNS servers to custom
3. Create Container App Environment in subnet of previous vnet (Workload profile is used)
4. Create a Container App that consume Kafka (Dapr is not used)
5. Setup scaling rule as above

Expected behavior [What you expected to happen.]

KEDA should resolve url 'xxxx.westeurope.azure.confluent.cloud' to X.240.Y.Z

Actual behavior [What actually happened.]

KEDA resolve url 'xxxx.westeurope.azure.confluent.cloud' to 10.1.0.4, so scaling doesn't works

Screenshots
If applicable, add screenshots to help explain your problem.
extacted from system logs :

VNET DNS configuration :

workload profile configuration :

Additional context

Begin with the provided reproduction steps for the Container Apps environment, custom VNET DNS, and Kafka scaling rule. Inspect the linked system logs and compare DNS resolution inside the consuming app with resolution from KEDA. Done means the Kafka hostname resolves to the private address X.240.Y.Z and scaling works.