# Unable to access Webinterface FHEM (Homeautomation) after installation of PI-Hole (DNS Problem)
**URL:** https://dietpi.com/forum/t/unable-to-access-webinterface-fhem-homeautomation-after-installation-of-pi-hole-dns-problem/23312
**Category:** Troubleshooting
**Created:** [23 April 2025 09:49 UTC](https://dietpi.com/forum/t/unable-to-access-webinterface-fhem-homeautomation-after-installation-of-pi-hole-dns-problem/23312 "2025-04-23T09:49:20Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@hmtec99](https://dietpi.com/forum/u/hmtec99)
#### Post date: [23 April 2025 09:49 UTC](https://dietpi.com/forum/t/unable-to-access-webinterface-fhem-homeautomation-after-installation-of-pi-hole-dns-problem/23312/1 "2025-04-23T09:49:20Z")
### Creating a bug report/issue
I have searched the existing open and closed issues
#### Required Information
- DietPi version | `cat /boot/dietpi/.version`
G\_DIETPI\_VERSION\_CORE=9
G\_DIETPI\_VERSION\_SUB=12
G\_DIETPI\_VERSION\_RC=1
G\_GITBRANCH=‘master’
G\_GITOWNER=‘MichaIng’
- Distro version | `echo $G_DISTRO_NAME $G_RASPBIAN`
bookworm
- Kernel version | `uname --all`
Linux server 5.10.66-27-rockchip-gea60d388902d #rockchip SMP Mon Oct 24 08:25:47 UTC 2022 aarch64 GNU/Linux
- Architecture | `dpkg --print-architecture`
arm64
- SBC model | `echo $G_HW_MODEL_NAME` or (EG: RPi3)
Generic Device (aarch64)
- Power supply used
other
- SD card used
other
#### Additional Information (if applicable)
- Software title
FHEM | Pi-Hole
- Was the software title installed freshly or updated/migrated?
Pi-Hole was freshly installed | FHEM was already installed (long ago)
- Can this issue be replicated on a fresh installation of DietPi
untested but I think so
← If you sent a “dietpi-bugreport”, please paste the ID here →
- Bug report ID | `echo $G_HW_UUID`
#### Steps to reproduce
1. Install Pi-Hole on a Diet-Pi-Server with existing services with webinterface
2. …
#### Expected behaviour
- Normal function of webinterface
#### Actual behaviour
- After installation of Pi-Hole the webinterface of another service on the same server isn’t accessible anymore over dns-name (until you stop pi-hole service)
#### Extra details
- FHEM service runs at [http://server:8083/fhem](http://server:8083/fhem) ([http://192.168.1.xxx:8083/fhem](http://192.168.1.xxx:8083/fhem) is accessible !)
- Pi-Hole service runs at [http://192.168.1.xxx:8089/admin/](http://192.168.1.xxx:8089/admin/)
You can’t open the Webinterface of FHEM by servername (DNS) while PI-Hole is running.
Do I have to add the servername to pi-hole manually for dns-resolution and how is this done (without domain)?
Thanks in advance.
hmtec
---
### Author:  [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [23 April 2025 10:09 UTC](https://dietpi.com/forum/t/unable-to-access-webinterface-fhem-homeautomation-after-installation-of-pi-hole-dns-problem/23312/2 "2025-04-23T10:09:29Z")
Pihole has a section where you can add custom DNS records
---
### Author:  [@hmtec99](https://dietpi.com/forum/u/hmtec99)
#### Post date: [23 April 2025 10:41 UTC](https://dietpi.com/forum/t/unable-to-access-webinterface-fhem-homeautomation-after-installation-of-pi-hole-dns-problem/23312/3 "2025-04-23T10:41:20Z")
I already tested this with servername only (without domain).
It do function with the pseudo-domain of the router after the servername (server.router.tld).
Thank you!
---
### Author:  [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [23 April 2025 11:07 UTC](https://dietpi.com/forum/t/unable-to-access-webinterface-fhem-homeautomation-after-installation-of-pi-hole-dns-problem/23312/4 "2025-04-23T11:07:14Z")
You can add whatever domain name to PiHole without using the pseudo domain of the router
---
### Author:  [@system](https://dietpi.com/forum/u/system)
#### Post date: [22 July 2025 11:08 UTC](https://dietpi.com/forum/t/unable-to-access-webinterface-fhem-homeautomation-after-installation-of-pi-hole-dns-problem/23312/5 "2025-07-22T11:08:00Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.