dear community,
I know that this topic has been discussed here many times, but after reading countless threads, I have not yet been able to solve the problem.
i hope i have included all the relevant information here so that you can get the best possible picture.
Pihole was installed as a container via Portainer. afterwards it was connected to traefik (static)
routers:
to-pihole:
rule: “Host(`pihole.xxxx.XXXX.eu`)”
tls:
certResolver: cloudflare
service: pihole
services:
pihole:
loadBalancer:
servers:
- url: http://10.75.0.100
Expected Behaviour:
about my setup:
Network 10.75.0.0/23
Fritzbox: 10.75.0.1
Synology NAS: 10.75.0.2 (with Synology DNS server)
PiHole (in the Portainer): 10.75.0.100
Unbound (in the container) 10.75.0.101
DHCP server (via Fritzbox) 10.75.1.1 - 10.75.1.254
DNS request currently runs as follows:
Client -> Pihole -> Synology DNS Server -> Unbound
- The clients receive the Pihole as DNS server from the FritzBox via DHCP
- conditional forwarding is set up in Pihole (Local network: 10.75.0.0/23 ; IP address of your DHCP server: 10.75.0.1 ; Local domain name: fritz.box)
- Upstream in Pihole is the Synology 10.75.0.2
- Upstream in the Fritzbox is Synology 10.75.0.2
- Synology DNS Server Limit source IP service: 10.75.0.100 and 10.75.0.2
- Synology DNS Server Upstream 10.75.0.101 (Unbound)
there is also no ipv6 in my entire network. it is switched off in the Fritzbox and in the synology.
Actual Behaviour:
it does not show any hostnames in my pihole.
as a small additional question (even if it doesn't quite fit in here):
does anyone have an idea why it happens again and again that some websites cannot be loaded properly (have to be reloaded several times, often takes up to 30 sec, are not displayed/built correctly the first time they are loaded) when I use unbound as upstream. if I set a public DNS like cloudflare as second upstream, this problem does not exist.
Debug Token:
https://tricorder.pi-hole.net/aWkYqQj3/
I know that this topic has been discussed here many times, but after reading countless threads, I have not yet been able to solve the problem.
i hope i have included all the relevant information here so that you can get the best possible picture.
Pihole was installed as a container via Portainer. afterwards it was connected to traefik (static)
routers:
to-pihole:
rule: “Host(`pihole.xxxx.XXXX.eu`)”
tls:
certResolver: cloudflare
service: pihole
services:
pihole:
loadBalancer:
servers:
- url: http://10.75.0.100
Expected Behaviour:
about my setup:
Network 10.75.0.0/23
Fritzbox: 10.75.0.1
Synology NAS: 10.75.0.2 (with Synology DNS server)
PiHole (in the Portainer): 10.75.0.100
Unbound (in the container) 10.75.0.101
DHCP server (via Fritzbox) 10.75.1.1 - 10.75.1.254
DNS request currently runs as follows:
Client -> Pihole -> Synology DNS Server -> Unbound
- The clients receive the Pihole as DNS server from the FritzBox via DHCP
- conditional forwarding is set up in Pihole (Local network: 10.75.0.0/23 ; IP address of your DHCP server: 10.75.0.1 ; Local domain name: fritz.box)
- Upstream in Pihole is the Synology 10.75.0.2
- Upstream in the Fritzbox is Synology 10.75.0.2
- Synology DNS Server Limit source IP service: 10.75.0.100 and 10.75.0.2
- Synology DNS Server Upstream 10.75.0.101 (Unbound)
there is also no ipv6 in my entire network. it is switched off in the Fritzbox and in the synology.
Actual Behaviour:
it does not show any hostnames in my pihole.
as a small additional question (even if it doesn't quite fit in here):
does anyone have an idea why it happens again and again that some websites cannot be loaded properly (have to be reloaded several times, often takes up to 30 sec, are not displayed/built correctly the first time they are loaded) when I use unbound as upstream. if I set a public DNS like cloudflare as second upstream, this problem does not exist.
Debug Token:
https://tricorder.pi-hole.net/aWkYqQj3/
Zuletzt bearbeitet:
