# Dns routing inside Kubernetes with Edge tunneler daemonset

**URL:** <https://openziti.discourse.group/t/dns-routing-inside-kubernetes-with-edge-tunneler-daemonset/2454>\
**Category:** Uncategorized\
**Created:** [April 20, 2024, 11:39pm UTC](https://openziti.discourse.group/t/dns-routing-inside-kubernetes-with-edge-tunneler-daemonset/2454 "2024-04-20T23:39:57Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\
**Post date:** [April 21, 2024, 8:08pm UTC](https://openziti.discourse.group/t/dns-routing-inside-kubernetes-with-edge-tunneler-daemonset/2454/2 "2024-04-21T20:08:36Z")

</div>

If you were successful using the NetFoundry console, there's functionally no difference presuming you've configured everything correctly. I understand what you're trying to do, but I don't see what the problem or question is that you have? Can you expand on the problem?

---

_[View the full topic](https://openziti.discourse.group/t/dns-routing-inside-kubernetes-with-edge-tunneler-daemonset/2454)._