# Dopper run w/ enable-dns-resolver timesout

**URL:** <https://community.doppler.com/t/dopper-run-w-enable-dns-resolver-timesout/1371>\
**Category:** Need Help\
**Created:** [October 18, 2023, 9:42pm UTC](https://community.doppler.com/t/dopper-run-w-enable-dns-resolver-timesout/1371 "2023-10-18T21:42:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![weilandia](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/weilandia/32/928_2.png) [@weilandia](https://community.doppler.com/u/weilandia)\
**Post date:** [October 18, 2023, 9:42pm UTC](https://community.doppler.com/t/dopper-run-w-enable-dns-resolver-timesout/1371/1 "2023-10-18T21:42:23Z")

</div>

Hello,

Per the docs recommendation, we put --enable-dns-resolver in our scripts because we were running into timeout issues.

Now it’s actually that flag that is causing timeout issues and things are running run without it. Just wanted to give a heads up:

/app # doppler --enable-dns-resolver --debug run – bundle exec rails c  
Debug: Using config dir /root/.doppler  
Debug: Using config file /root/.doppler/.doppler.yaml  
Debug: Reading config file  
Debug: Skipping CLI upgrade check due to disallowed command  
Debug: Using metadata file /root/.doppler/fallback/.metadata-c865b4b86088814fed5c3a3a8275c16a5f3e1bf16c387a48072ca2a3024a9b24.json  
Debug: Reading metadata file /root/.doppler/fallback/.metadata-c865b4b86088814fed5c3a3a8275c16a5f3e1bf16c387a48072ca2a3024a9b24.json  
Debug: Using custom DNS resolver 1.1.1.1:53  
Debug: Performing HTTP GET to [https://api.doppler.com/v3/configs/config/secrets/download?config=&format=json&include\_dynamic\_secrets=true&project=](https://api.doppler.com/v3/configs/config/secrets/download?config=&format=json&include_dynamic_secrets=true&project=)  
Debug: Sending anonymous analytics payload: ‘{“command”:“doppler.run”}’  
Debug: Using custom DNS resolver 1.1.1.1:53

---

<div class="post-metadata">

**Author:** ![weilandia](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/weilandia/32/928_2.png) [@weilandia](https://community.doppler.com/u/weilandia)\
**Post date:** [October 18, 2023, 9:43pm UTC](https://community.doppler.com/t/dopper-run-w-enable-dns-resolver-timesout/1371/2 "2023-10-18T21:43:08Z")

</div>

I can’t post the full backtrace because this service says I can only make posts with less than two links in the post since I’m new.

---

<div class="post-metadata">

**Author:** ![watsonian](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/watsonian/32/267_2.png) [@watsonian](https://community.doppler.com/u/watsonian)\
**Post date:** [October 18, 2023, 9:55pm UTC](https://community.doppler.com/t/dopper-run-w-enable-dns-resolver-timesout/1371/3 "2023-10-18T21:55:52Z")

</div>

Hi @weilandia!

Welcome to the Doppler Community!

Can you try posting again? This time, use two sets of three backticks (`) to wrap the backtrace like this:

![CleanShot 2023-10-18 at 16.54.25](https://us1.discourse-cdn.com/flex016/uploads/doppler/original/1X/75be1baea0890ce36fc6ec37fda8273fda63cc6b.png)

Typically, if you’re still having timeout issues after switching to the custom DNS resolver, then there’s likely some kind of network accessibility issue in your environment. Are you able to ssh into or attach to the machine and run commands by hand? If so, could you see if curling other URLs works too?

Regards,  
-Joel