# Ziti Tunneller complaining "not find a way to configure system resolver"

**URL:** <https://openziti.discourse.group/t/ziti-tunneller-complaining-not-find-a-way-to-configure-system-resolver/446>\
**Category:** Ziti Edge Tunnel\
**Created:** [April 27, 2022, 5:55pm UTC](https://openziti.discourse.group/t/ziti-tunneller-complaining-not-find-a-way-to-configure-system-resolver/446 "2022-04-27T17:55:22Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![sameersarkar-tcl](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/sameersarkar-tcl/32/75_2.png) [@sameersarkar-tcl](https://openziti.discourse.group/u/sameersarkar-tcl)\
**Post date:** [May 1, 2022, 3:38pm UTC](https://openziti.discourse.group/t/ziti-tunneller-complaining-not-find-a-way-to-configure-system-resolver/446/15 "2022-05-01T15:38:55Z")

</div>

Hi @TheLumberjack , @qrkourier ,  
My problem statement is very simple.  
The ziti-edge-tunneller binary is not running from within openziti/quickstart docker container.  
It is giving the DNS problem as stated by me above and in [Launched openziti network using docker compose, but client not able to fetch simple blue service - #14 by dovholuknf](https://openziti.discourse.group/t/launched-openziti-network-using-docker-compose-but-client-not-able-to-fetch-simple-blue-service/444/14)

But it looks like the DNS configuration issue is not causing my problem as clarified by @TheLumberjack in [Launched openziti network using docker compose, but client not able to fetch simple blue service - #14 by dovholuknf](https://openziti.discourse.group/t/launched-openziti-network-using-docker-compose-but-client-not-able-to-fetch-simple-blue-service/444/14)

But something is.

---

_[View the full topic](https://openziti.discourse.group/t/ziti-tunneller-complaining-not-find-a-way-to-configure-system-resolver/446)._