# Enable private IP address crawls

**URL:** <https://discuss.elastic.co/t/enable-private-ip-address-crawls/284206>\
**Category:** Elastic Search\
**Created:** [September 14, 2021, 4:40pm UTC](https://discuss.elastic.co/t/enable-private-ip-address-crawls/284206 "2021-09-14T16:40:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lgoolsby](https://avatars.discourse-cdn.com/v4/letter/l/90db22/32.png) [@lgoolsby](https://discuss.elastic.co/u/lgoolsby)\
**Post date:** [September 14, 2021, 4:40pm UTC](https://discuss.elastic.co/t/enable-private-ip-address-crawls/284206/1 "2021-09-14T16:40:06Z")

</div>

I am setting up App Search and need to crawl some internal content. I found [this post](https://discuss.elastic.co/t/web-crawler-failed-http-request-unable-to-request-domain-because-it-resolved-to-only-private-invalid-addresses/270631) that says the feature is coming in the next minor patch, but it wasn't clear which version that will be. Will it be a patch based off 7.14 or does 7.14 already include it? If 7.14 includes the new feature how do we toggle it?

---

<div class="post-metadata">

**Author:** ![oleksiy-elastic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/oleksiy-elastic/32/49074_2.png) [@oleksiy-elastic](https://discuss.elastic.co/u/oleksiy-elastic)\
**Post date:** [September 14, 2021, 4:57pm UTC](https://discuss.elastic.co/t/enable-private-ip-address-crawls/284206/2 "2021-09-14T16:57:27Z")

</div>

Hello, Lane,

Thank you for trying out our new web crawler!

You can check your `enterprise-search.yml` file for the following two settings (those have been around for quite some time now):

```auto
# -----------------------------
# Crawler DNS Security Controls
# -----------------------------
#
# WARNING: The settings in this section could make your deployment vulnerable to
# SSRF attacks (especially in cloud environments) from the owners of any domains
# you crawl. Do not enable any of the settings here unless you fully control DNS
# domains you access with the crawler.
#
# See https://owasp.org/www-community/attacks/Server_Side_Request_Forgery for
# more details on the SSRF attack and the risks associated with it.
#
# Allow crawler to access the localhost (127.0.0.0/8 IP namespace)
#
#crawler.security.dns.allow_loopback_access: false
#
# Allow crawler to access the private IP space: link-local, network-local addresses, etc
# (see https://en.wikipedia.org/wiki/Reserved_IP_addresses#IPv4 for more details)
#
#crawler.security.dns.allow_private_networks_access: false

```

Those should allow you to control where the crawler is allowed to go.

Please note: Those are not available on Elastic Cloud for security reasons.

---

<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 4, 2022, 8:32am UTC](https://discuss.elastic.co/t/enable-private-ip-address-crawls/284206/3 "2022-11-04T08:32:19Z")

</div>