# Unknown host in runner logs, ECE 3.5.1 install fails

**URL:** <https://discuss.elastic.co/t/unknown-host-in-runner-logs-ece-3-5-1-install-fails/373036>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Tags:** docker\
**Created:** [January 9, 2025, 10:39pm UTC](https://discuss.elastic.co/t/unknown-host-in-runner-logs-ece-3-5-1-install-fails/373036 "2025-01-09T22:39:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kcsofl](https://avatars.discourse-cdn.com/v4/letter/k/d9b06d/32.png) [@kcsofl](https://discuss.elastic.co/u/kcsofl)\
**Post date:** [January 9, 2025, 10:39pm UTC](https://discuss.elastic.co/t/unknown-host-in-runner-logs-ece-3-5-1-install-fails/373036/1 "2025-01-09T22:39:22Z")

</div>

We saw a problem with installing ece 3.5.1 on a new ec2 instance in aws. All pre-reqs were followed but despite this we kept seeing "unknown host" exeptions in the logs in /mnt/data/elastic/services/%hostname%/logs/runner.  
We also noticed a behavior where name resolution inside a container was not working, despite /etc/hosts and /etc/resolv.conf being correct.

The fix for us was to 'disable' the nscd daemon or,

- sudo systemctl stop nscd
- sudo systemctl disable nscd

Once this was done and the ece install was re-started, the containers started to have name resolution again.  
(Example test was, docker exec %podname% ping %podname% which had preivously failed. )