Losing internet connection when using TrueNAS Pi-hole app for static DNS

Help Community Help
1

The issue I am facing:

Whenever I set my routers dns towards my pi-hole, I lose my internet connection.
And when I try using ''nslookup google.com" it'll say that it can't find the server.

Details about my system:

I'm using TrueNas Scale and installed pi-hole as an app, though I am pretty new to having my own homelab, I'm trying to learn more stuff about all this.
I'm still using my router (zyxel vmg8825-t50) as DHCP

What I have changed since installing Pi-hole:

I've tried reinstalling pi-hole with different settings I found across numerous of different guides to installing pi-hole.
I've played with the routers firewall settings with no success though honestly, I'm not the brightest I might've looked over something.

My debug token: nJraDVSk

2

You seem to be a running your Pi-hole in a Docker container?
If that would be true, please consider to set the recommended FTLCONF_LOCAL_IPV4 environment variable.

Run from a client that you expect to use Pi-hole for DNS, what's the output of the following commands?

nslookup pi.hole

nslookup flurry.com

Please share the complete outpout, preferably as text.

3

nslookup pi.hole
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.93

DNS request timed out.
timeout was 2 seconds.

nslookup flurry.com
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.93

DNS request timed out.
timeout was 2 seconds.

4

Commonly, Pi-hole would not require any changes in your router's firewall.
In case you've openened them, make sure that inbound ports 53 and 80 are closed for traffic on your router.

For a firewall potentially running on the machine hosting Pi-hole, refer to Pi-hole's documentation on required ports and related firewall examples.

What machine is 192.168.1.93?
Is that your Pi-hole host?

5

Yes, that would be my server

6

Then your output would suggest that those DNS requests were using the correct IP, but never made it to Pi-hole.
You should be able to confirm this by inspecting Pi-hole's Query Log:
If those nslookups do not result in respective log entries, then Pi-hole never received them.

This would in turn suggest that something is blocking those DNS requests.

Check your host machine's firewall as well as your Pi-hole's VM/Docker configuration to allow access to Pi-hole's ports. Please refer to respective links as provided in my previous post.

7

I think I've opened up those ports now but with no success

edit:
nc –zv 192.168.1.93 53
I looked at the ports and they all seem to be open, except for 53.
Though I'm not sure how to open this one, I thought I did but as we can see it didn't work.

8

What's the result of running the following command on your 192.168.1.93 Pi-hole host machine:

sudo ss -tulpn | grep "Netid\|:53"
9 
Netid State  Recv-Q Send-Q                             Local Address:Port  Peer Address:PortProcess                                                    
udp   UNCONN 0      0                                        0.0.0.0:53885      0.0.0.0:*    users:(("wsdd.py",pid=921223,fd=34))                      
udp   UNCONN 0      0                                        0.0.0.0:5353       0.0.0.0:*    users:(("avahi-daemon",pid=921204,fd=13))                 
tcp   LISTEN 0      5                                     172.17.0.1:5357       0.0.0.0:*    users:(("wsdd.py",pid=921223,fd=44))                      
tcp   LISTEN 0      5                                  172.17.57.172:5357       0.0.0.0:*    users:(("wsdd.py",pid=921223,fd=40))                      
tcp   LISTEN 0      5                                    172.17.0.10:5357       0.0.0.0:*    users:(("wsdd.py",pid=921223,fd=36))                      
tcp   LISTEN 0      5                                 172.17.250.160:5357       0.0.0.0:*    users:(("wsdd.py",pid=921223,fd=32))                      
tcp   LISTEN 0      5                                 172.17.211.213:5357       0.0.0.0:*    users:(("wsdd.py",pid=921223,fd=28))                      
tcp   LISTEN 0      5                                  172.17.205.10:5357       0.0.0.0:*    users:(("wsdd.py",pid=921223,fd=24))                      
tcp   LISTEN 0      5                                  172.17.46.213:5357       0.0.0.0:*    users:(("wsdd.py",pid=921223,fd=20))                      
tcp   LISTEN 0      5                                  172.17.179.84:5357       0.0.0.0:*    users:(("wsdd.py",pid=921223,fd=16))                      
tcp   LISTEN 0      5                                     172.16.0.1:5357       0.0.0.0:*    users:(("wsdd.py",pid=921223,fd=12))                      
tcp   LISTEN 0      5                                   192.168.1.93:5357       0.0.0.0:*    users:(("wsdd.py",pid=921223,fd=8))                       
tcp   LISTEN 0      5      [fe80::2cf7:72ff:fe64:85b9]%kube-dummy-if:5357          [::]:*    users:(("wsdd.py",pid=921223,fd=56))                      
tcp   LISTEN 0      5        [fe80::2045:5eff:fe0c:2630]%kube-bridge:5357          [::]:*    users:(("wsdd.py",pid=921223,fd=52))                      
tcp   LISTEN 0      5              [fe80::1ac0:4dff:fe73:c7e]%enp4s0:5357          [::]:*    users:(("wsdd.py",pid=921223,fd=48))
10

There is nothing that listens on port 53 on your host machine.

Whatever is hosting your Pi-hole (VM/Docker/Kubernetes/...), you'd need to configure it to listen on its outward facing port 53 (UDP/TCP) and connect those to your Pi-hole environment's internal port 53. Similar would apply to Pi-hole's other required ports, if you'd want to access Pi-hole's corresponding services.

11

how would I go on about doing that? I'm quite new to networking / linux-based things

12

Sorry, I can't provide more detailed help for that.

Note that TrueNAS Scale is not an OS supported by Pi-hole, and neither would the Pi-hole team provide an app for that platform.

You'd have to consult respective documentation and support for TrueNas Scale.
If you indeed installed some kind of Pi-hole app for TrueNAS, you also should consider to contact its respective maintainers for support.

13

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