# Occasional "couldnt\_resolve\_host" error?

**URL:** <https://discuss.elastic.co/t/occasional-couldnt-resolve-host-error/35004>\
**Category:** Elasticsearch\
**Created:** [November 19, 2015, 12:15am UTC](https://discuss.elastic.co/t/occasional-couldnt-resolve-host-error/35004 "2015-11-19T00:15:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![frances](https://avatars.discourse-cdn.com/v4/letter/f/ea666f/32.png) [@frances](https://discuss.elastic.co/u/frances)\
**Post date:** [November 19, 2015, 12:15am UTC](https://discuss.elastic.co/t/occasional-couldnt-resolve-host-error/35004/1 "2015-11-19T00:15:10Z")

</div>

I'm running into this error quite a few times with my instance and I'm wondering why:

ETHON: performed EASY effective\_url=https://.us-east-1.aws.found.io:/myindex/docs/\_search?from=0&size=20 response\_code=0 return\_code=couldnt\_resolve\_host total\_time=6.4e-05  
ETHON: performed EASY effective\_url=https://.us-east-1.aws.found.io:/myindex/docs/\_search?from=0&size=20 response\_code=0 return\_code=couldnt\_resolve\_host total\_time=4.9e-05

So it seems there was some sort of retry on the Rails gem's side, but it still couldn't resolve the host. This happened at approximately 2015-11-18 15:59:16 -0800

Does anyone know what's going on here and how I can protect against it? I'm using the rails gem and there doesn't seem to be a way to detect it until it actually executes the query. It's a gnarly error!

I should also mention that I am on ES 1.7.3

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:37pm UTC](https://discuss.elastic.co/t/occasional-couldnt-resolve-host-error/35004/2 "2017-07-05T23:37:28Z")

</div>

Closed on July 5, 2017, 11:37pm UTC