Unable to access Webinterface FHEM (Homeautomation) after installation of PI-Hole (DNS Problem)

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

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

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

Pihole has a section where you can add custom DNS records

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!

You can add whatever domain name to PiHole without using the pseudo domain of the router

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.