# Pi-hole install script and dhcpcd.conf

**URL:** <https://discourse.pi-hole.net/t/pi-hole-install-script-and-dhcpcd-conf/48047>\
**Category:** Community Help\
**Created:** [July 5, 2021, 2:49pm UTC](https://discourse.pi-hole.net/t/pi-hole-install-script-and-dhcpcd-conf/48047 "2021-07-05T14:49:11Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![Roo](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/roo/32/25976_2.png) [@Roo](https://discourse.pi-hole.net/u/Roo)\
**Post date:** [July 5, 2021, 10:45pm UTC](https://discourse.pi-hole.net/t/pi-hole-install-script-and-dhcpcd-conf/48047/11 "2021-07-05T22:45:59Z")

</div>

> [@deHakkelaar](#):
>
> I dont use my Pihole host as a desktop or anything so the daemons/processes running on it dont need to know my client hostnames (EDIT: and I dont want them to).

You're missing the point that this default configuration is causing lots of non-fatal errors to appear in the logs.

For whatever reason, when you issue `sudo` on Ubuntu, it does a name lookup. With the way that pi-hole goes and whacks the DNS when it configures a static IP for you - it breaks the ability to look up the /etc/hostname name. That's messed up.

Someone even posted a problem about this a while back - [\*\*\* SECURITY information for my-server \*\*\* problem with defaults entries](https://discourse.pi-hole.net/t/security-information-for-my-server-problem-with-defaults-entries/41005) - that issue closed because the person didn't continue to participate.

Again, my primary concern is that the install script, in the situation where you have a dynamic IP of the host - is tossing all sorts of error logs. That's not right.

Honestly - it's fine if the pi-hole never uses local lookups - but it should be able to resolve the /etc/hostname name.. (which is why I hacked /etc/hosts to fix it for my configuration)

---

_[View the full topic](https://discourse.pi-hole.net/t/pi-hole-install-script-and-dhcpcd-conf/48047)._