First time user of pi-hole, can't make it work

Expected Behaviour:

Hi! I'm (trying) to setup a pi-hole on ubuntu 20.10 and and huawei model b252s-23a. Im using the pi-hole as my DHCP server and pi-hole version us v5.2.3, AdminLTE v5.3, FTL v5.4. The localhost's ip is 127.0.0.1. I'd think that with this in mind my devices should connect to the pi-hole succesfully and i'd get use the internet and enjoy an ad-free expierence.

Actual Behaviour:

nslookup pihole 196.168.8.201
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 196.168.8.201

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

My devices don't connect to it and the pi-hole's dashboard doesn't show more than 1 (localhost). I've done my best to include everything I think you need to help me.

Debug Token:

ydpy0q4m40

This is my first ever time posting here or even using pi-hole, so i'm sorry if some vital info is missing. There probably are some duplicates of this, but i've tried my best to go through them and so far nothing has helped

Edit: fixed typo of my pi-hole's ip and through some console commands i've found the ability to change my DNS server. So i have enabled my router(&disabled pihole) as my DHCP server and put the ip of my pihole as the primary & secondary dns servers, but this just leads to not being to open any websites (it can't find them). I've also done my best to go through my router's security settings to find possible problems. Also im usint ubuntu as a Vm. Here are some new screenshots some new pics regarding pihole - Album on Imgur.

Sounds as if some firewall is blocking 53 TCP + UDP:

Below is permissive allowing all:

pi@ph5:~ $ sudo iptables -nL
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Also check your router for security related settings that might block DNS queries on your LAN.

EDIT: ow ps, you should query for pi.hole instead of pihole eg:

nslookup pi.hole 196.198.8.201

EDIT2: And another note, that 196.198.8.201 IP address is a public IP!
You wont get support here if you run an "open resolver" that can be abused to direct an attack on other victims:

http://www.openresolver.com/

You have network issues: Your router is still active as DHCP server and advertises itself as DNS server. Additionally, two different IP ranges exist in your network (10.0.2.0/24 and 192.168.8.0/24) - I guess this is not on purpose?

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the enp0s3 interface:
   10.0.2.15/24 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
   192.168.8.201/32 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)


   * Received 548 bytes from enp0s3:10.0.2.2
     Offered IP address: 10.0.2.15
     Server IP address: 10.0.2.4
     Relay-agent IP address: N/A
     BOOTP server: (empty)
     BOOTP file: pihole_ubuntu.pxe
     DHCP options:
      Message type: DHCPOFFER (2)
      netmask: 255.255.255.0
      router: 10.0.2.2
      dns-server: 192.168.8.1


*** [ DIAGNOSING ]: Setup variables
    PIHOLE_INTERFACE=enp0s3
    IPV4_ADDRESS=192.168.8.201
    IPV6_ADDRESS=
    QUERY_LOGGING=true
    INSTALL_WEB_SERVER=true
    INSTALL_WEB_INTERFACE=true
    LIGHTTPD_ENABLED=true
    CACHE_SIZE=10000
    BLOCKING_ENABLED=true
    DNSMASQ_LISTENING=local
    PIHOLE_DNS_1=9.9.9.9
    PIHOLE_DNS_2=149.112.112.112
    DNS_FQDN_REQUIRED=true
    DNS_BOGUS_PRIV=true
    DNSSEC=false
    REV_SERVER=false
    DHCP_ACTIVE=true
    DHCP_START=192.168.8.100
    DHCP_END=192.168.8.251
    DHCP_ROUTER=192.168.8.1
    DHCP_LEASETIME=24
    PIHOLE_DOMAIN=lan
    DHCP_IPv6=true
    DHCP_rapid_commit=false

Hi! After some researching I found a way to show my dns setting through some console lines. So i've tried something new and disabled my pihole's DCHP server and instead enabled my router as my DCHP server. This just leads to me not being able to open any websites because i guess the devices can't connect to the pi-hole?

Here are some new screenshots:

PS. I'm also new to networking in general and so I have no idea for example why i would have to different ip ranges? Maybe something to do with hamachi or zerotier?

Where is that Pi-hole instance running ?
On a Pi, some other hardware or maybe a VM in the cloud ?

1 Like

So sorry about this mistake, i've accidentally put the given ip as 196.198.8.201 instead of the actual ip: 196.168.8.201 and btw thanks for the notice of the vulnerability of my sys. I've tested the correct ip and it seems to be safe.

Do you mean 192.168.8.201 ?

Below the range of private IPv4 addresses:

Its running on a old laptop with ubuntu as a vm

What does this mean and how would i get rid of the other one?

I would start by deciding which device should be the DHCP server - Pi-hole or your router and disable it on the other, respectively.

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