Resolve DNS - Not using full qualified dns name

[bgc-gustavo-vieira]

Report

Hey! I am having issues with the interceptor. I installed it in the keda namespace and created de HTTPScaledObject as well as my service and deployment in another namespace.
When I call the proxy/interceptor it cannot resolve the domain because it uses [service name].[namespace] instead of using FQDN [service name].[namespace].svc.cluster.local. Is there a reason to this decision?
Could this be changed?

Expected Behavior

I would like that the interceptor uses the FQDN [service name].[namespace].svc.cluster.local

Actual Behavior

He uses a short version [service name].[namespace]

Steps to Reproduce the Problem

Logs from KEDA HTTP operator

2025-09-30T13:56:47Z    ERROR   LoggingMiddleware.RoutingMiddleware.CountingMiddleware.UpstreamHandler.StaticHandler    Bad Gateway     {"routingKey": "//unflare.dev-bgcbrasil.com.br/health/", "namespacedName": {"name":"SCALER_NAME","namespace":"SERVICE_NAMESPACE_NAME"}, "stream": "http://SERVICE_NAME.SERVICE_NAMESPACE_NAME:8080/health", "error": "net/http: timeout awaiting response headers"}

2025-09-29T20:21:50Z ERROR LoggingMiddleware.RoutingMiddleware.CountingMiddleware.UpstreamHandler.StaticHandler Bad Gateway {"routingKey": "//unflare.dev-bgcbrasil.com.br/health/", "namespacedName": {"name":"SCALER_NAME","namespace":"SERVICE_NAMESPACE_NAME"}, "stream": "http://SERVICE_NAME.SERVICE_NAMESPACE_NAME:8080/health", "error": "dial tcp: lookup SERVICE_NAME.SERVICE_NAMESPACE_NAME: i/o timeout"}

HTTP Add-on Version

0.10.0

Kubernetes Version

Other

Platform

Amazon Web Services

Anything else?

I am using Kubernetes Version 1.33

[wozniakjan]

Could this be changed?

are you willing to implement the change? It should be optional to set the cluster domain and not hardcoded to .cluster.local with the current behavior as default, because it is configurable and under full control of the K8s cluster operator / admin.

Also worth noting, Kubernetes internal DNS model specifies that all these should resolve the same way:

• svc_name.svc_namespace
• svc_name.svc_namespace.svc.cluster.local

https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/

you may need to check your dnsPolicy or NetworkPolicy because these can alter the behavior of DNS resolution. And afaict from "net/http: timeout awaiting response headers", it seems like the interceptor resolved the domain name correctly to an IP address and then it failed to get HTTP response in time (possibly didn't manage to establish TCP session)