# Web crawler DNS name resolution failed while validating domain

**URL:** <https://discuss.elastic.co/t/web-crawler-dns-name-resolution-failed-while-validating-domain/344356>\
**Category:** Elastic Search\
**Tags:** elastic-app-search\
**Created:** [October 4, 2023, 6:07am UTC](https://discuss.elastic.co/t/web-crawler-dns-name-resolution-failed-while-validating-domain/344356 "2023-10-04T06:07:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sivagurlinka](https://avatars.discourse-cdn.com/v4/letter/s/a6a055/32.png) [@sivagurlinka](https://discuss.elastic.co/u/sivagurlinka)\
**Post date:** [October 4, 2023, 6:07am UTC](https://discuss.elastic.co/t/web-crawler-dns-name-resolution-failed-while-validating-domain/344356/1 "2023-10-04T06:07:43Z")

</div>

While trying to validate the domain we are getting _"DNS name resolution failed. No suitable addresses found!"_ and we are able to access URL from browser.  
we have standalone Elasticsearch running on windows and Enterprisesearch configured on Linux VM.  
We are able to crawl internal URL's but not public, we also tried adding below configs to enterprise search. please suggest possible solutions to resolve this.

```auto
connector.crawler.http.proxy.host: xxxxxxxxxxxxxx
connector.crawler.http.proxy.port: 8080
connector.crawler.http.proxy.protocol: https
connector.crawler.security.dns.allow_private_networks_access: true
connector.crawler.security.dns.allow_loopback_access: true

crawler.http.proxy.host: xxxxxxxxxxx
crawler.http.proxy.port: 8080
crawler.http.proxy.protocol: https
crawler.security.dns.allow_loopback_access: true
crawler.security.dns.allow_private_networks_access: true

```

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/7/071f49ff4b55949faca9857b1b5f14ef06fdaf54.png)

---

<div class="post-metadata">

**Author:** ![Carlos\_D](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_d/32/126245_2.png) [@Carlos\_D](https://discuss.elastic.co/u/Carlos_D)\
**Post date:** [October 4, 2023, 7:22am UTC](https://discuss.elastic.co/t/web-crawler-dns-name-resolution-failed-while-validating-domain/344356/2 "2023-10-04T07:22:07Z")

</div>

Hi @sivagurlinka !

DNS resolution should not be checked when a proxy is being used. Can you please double check that the configuration you used is actually getting picked up by Enterprise Search?

The configuration you are providing is both for the Elastic web crawler and the App Search web crawler. What is the crawler you are using to perform the check?

---

<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:** [November 1, 2023, 7:22am UTC](https://discuss.elastic.co/t/web-crawler-dns-name-resolution-failed-while-validating-domain/344356/3 "2023-11-01T07:22:44Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.