# Kubernetes Integration - DNS Issue

**URL:** <https://discuss.elastic.co/t/kubernetes-integration-dns-issue/376772>\
**Category:** Elastic Agent\
**Created:** [April 3, 2025, 9:49pm UTC](https://discuss.elastic.co/t/kubernetes-integration-dns-issue/376772 "2025-04-03T21:49:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![erikg](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@erikg](https://discuss.elastic.co/u/erikg)\
**Post date:** [April 3, 2025, 9:49pm UTC](https://discuss.elastic.co/t/kubernetes-integration-dns-issue/376772/1 "2025-04-03T21:49:29Z")

</div>

Hello,

I noticed part of the K8S integration is grabbing from:

```auto

https://${env.NODE_NAME}:10250

```

The issue is that this is dependent on DNS Resolution and leads to errors:  
`> error making http request: Get "https://<redacted>:10250/stats/summary": lookup <redacted>:53: no such host`

What can I use instead? I tried `${env.NODE_IP}` but that didn't work lol

---

<div class="post-metadata">

**Author:** ![erikg](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@erikg](https://discuss.elastic.co/u/erikg)\
**Post date:** [April 3, 2025, 10:07pm UTC](https://discuss.elastic.co/t/kubernetes-integration-dns-issue/376772/2 "2025-04-03T22:07:26Z")

</div>

I see that this environment variable comes not from Kubernetes directly but from the elastic agent install yaml

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/e/5e90a93c973a5e658aaabbe43e65c5249d837277.png)  
Ughhh!!!

So I will test out adding NODE\_IP and fieldPath: status.hostIP

---

<div class="post-metadata">

**Author:** ![erikg](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@erikg](https://discuss.elastic.co/u/erikg)\
**Post date:** [April 4, 2025, 3:51am UTC](https://discuss.elastic.co/t/kubernetes-integration-dns-issue/376772/3 "2025-04-04T03:51:30Z")

</div>

It worked!

By adding:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/7/c749df645af3441748c2b7a3c83781870848d45d.png)  
Then updating the Kubernetes integration to use  
`https://${env.NODE_IP}:10250`

I know have data coming in

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/9/593c7c4ede1e6771d9e645f100f3da9e4ac78547.png)
