## System Information * Pi-hole v4.0.0 ## Problem/Motivation I installed the piHole addon via the Hass.io Addon-Store and configured two custom domains: ``` { "update_lists_on_start": false, "ssl": true, "certfile": "fullchain.pem", "keyfile": "privkey.pem", "interface": "", "ipv6": true, "ipv4_address": "", "ipv6_address": "", "virtual_host": "", "hosts": [ { "name": "hass.home", "ip": "192.168.178.61" }, { "name": "mqtt.home", "ip": "192.168.178.61" } ] } ```` ## Expected behavior I expect to happen that `mqtt.home` will resolve to `192.168.178.61` ## Actual behavior ``` $ ping mqtt.home ping: cannot resolve mqtt.home: Unknown host ``` ## Steps to reproduce 1. Install the Hass.io AddOn 2. Configure it like above and re-route your DNS to your piHole 3. Flush your DNS 4. Try to resolve `mqtt.home` ## Proposed changes In https://github.com/hassio-addons/addon-pi-hole/blame/8e998e99f6ef20cd71b15c14e8989348315fe2e0/pi-hole/rootfs/etc/cont-init.d/pihole.sh#L199 the `hosts` configuration is written to `/etc/hosts.list`. I can also confirm this, while login into the piHole docker container: ``` root@a0d7b954-pi-hole:/$ cat /etc/hosts.list 192.168.178.61 hass.home 192.168.178.61 mqtt.home ``` Based on my knowledge, the file `/etc/hosts.list` is not used or included in any of the applications _piHole_ or _dnsmasq_. I guess the data should be written to `/etc/hosts`. This is one possible solution. And from what I know, this would also work (not tested yet). It is proposed in https://github.com/pi-hole/pi-hole/issues/975 A cleaner way would be using _dnsmasq_ and adding custom DNS records. This is described by @Zixim in https://github.com/pi-hole/pi-hole/issues/975#issuecomment-548375915

GitHub
hassio-addons/addon-pi-hole
Pi-hole - Community Hass.io Add-on for Home Assistant - hassio-addons/addon-pi-hole

Config setting for `hosts` don't work, because it uses /etc/hosts.list instead of /etc/hosts #115

Company

Community

Support

Connect