# \[Feature Request\] Local Host Resolution by Network

**URL:** https://discourse.pi-hole.net/t/feature-request-local-host-resolution-by-network/21049
**Category:** Duplicate
**Created:** [June 25, 2019, 9:58am UTC](https://discourse.pi-hole.net/t/feature-request-local-host-resolution-by-network/21049 "2019-06-25T09:58:10Z")
**Posts on this page:** 1
**Showing post:** 11

<div class="post-metadata">

### Author: ![CharAznable](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/c/5daacb/32.png) [@CharAznable](https://discourse.pi-hole.net/u/CharAznable)
#### Post date: [July 4, 2019, 8:59am UTC](https://discourse.pi-hole.net/t/feature-request-local-host-resolution-by-network/21049/11 "2019-07-04T08:59:43Z")

</div>

Since that fixed the issue, I now am curious as to why the 172 entry causes this. Could this be a bug with dnsmasq? Or pihole itself? Or is this expected since the network defined overlaps the server that is going to be resolving the network.

---

_[View the full topic](https://discourse.pi-hole.net/t/feature-request-local-host-resolution-by-network/21049)._