# Binder deployed in AWS EKS - domain name resolution errors

**URL:** <https://discourse.jupyter.org/t/binder-deployed-in-aws-eks-domain-name-resolution-errors/766>\
**Category:** Binder\
**Created:** [April 10, 2019, 8:14pm UTC](https://discourse.jupyter.org/t/binder-deployed-in-aws-eks-domain-name-resolution-errors/766 "2019-04-10T20:14:17Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![hhuuggoo](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/hhuuggoo/32/242_2.png) [@hhuuggoo](https://discourse.jupyter.org/u/hhuuggoo)\
**Post date:** [May 16, 2019, 4:15pm UTC](https://discourse.jupyter.org/t/binder-deployed-in-aws-eks-domain-name-resolution-errors/766/14 "2019-05-16T16:15:33Z")

</div>

I just ran into this issue - I’m not deploying binderhub, but I am deploying an app that uses repo2docker. fwiw - I’m using terraform, which is pretty nice, and for terraform, the workaround is here:

> <https://github.com/terraform-aws-modules/terraform-aws-eks/blob/a9753e8303cb2a0827a432cde96ddd0aee7aa931/docs/enable-docker-bridge-network.md>

---

_[View the full topic](https://discourse.jupyter.org/t/binder-deployed-in-aws-eks-domain-name-resolution-errors/766)._