DNS wont resolve :(

[RustedBuckett]

Still not working, should I reboot the pi-hole?

That's weird I don't remember naming it localhost, any way i can change this?

[deHakkelaar]

@RustedBuckett

Should I reboot the pi-hole?

No, we only reboot for a kernel update
Did the nslookups run succesfull ?

@RustedBuckett

any way i can change this?

Can change hostname with below:

sudo hostnamectl set-hostname <NEW_HOSTNAME>

And make sure that same name is reflected in below file:

pi@noads:~ $ cat /etc/hosts
127.0.0.1       localhost
::1             localhost ip6-localhost ip6-loopback
ff02::1         ip6-allnodes
ff02::2         ip6-allrouters

127.0.1.1       noads.dehakkelaar.nl  noads

[RustedBuckett]

nslookups timed out like earlier

[deHakkelaar]

And when run on Pi-hole ?

@deHakkelaar

And try do a lookup agian from one of your clients (can also try run localy on Pi-hole):

nslookup -class=chaos -type=txt version.bind 192.168.1.101

nslookup pi.hole 192.168.1.101

nslookup pi-hole.net 192.168.1.101

[RustedBuckett]

On pi-hole:

[root@bucket ~]# nslookup -class=chaos -type=txt version.bind 192.168.1.101
Server:         192.168.1.101
Address:        192.168.1.101#53

version.bind    text = "dnsmasq-pi-hole-2.81"

[root@bucket ~]# nslookup pi.hole 192.168.1.101
Server:         192.168.1.101
Address:        192.168.1.101#53

Name:   pi.hole
Address: 192.168.1.101

[root@bucket ~]# nslookup pi-hole.net 192.168.1.101
Server:         192.168.1.101
Address:        192.168.1.101#53

Non-authoritative answer:
Name:   pi-hole.net
Address: 192.124.249.118

[deHakkelaar]

That looks all good now.
Firewall could still drop though:

Admin page shows FTL Offline | Unable to start, cannot access dhcp.leases

Below ones seems to do the trick: sudo iptables -F sudo iptables -X sudo iptables -t nat -F sudo iptables -t nat -X sudo iptables -t nat -L -n -v sudo iptables -t mangle -F sudo iptables -t mangle -X sudo iptables -P INPUT ACCEPT sudo iptables -P OUTPUT ACCEPT sudo iptables -P FORWARD ACCEPT Check afterwards with: pi@noads:~ $ sudo iptables -L -n Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source …

And some routers got some kind of rebind protection.
Check your router settings for similar!

Why won't Pi-hole work with DNS rebind protection enabled?

What is DNS rebind protection? If your router has an option called DNS rebind protection enabled, you may run into issues when trying to use Pi-hole as your DNS server. The reasons for this are quite technical, but to summarize what this option does in one sentence: DNS rebind protection does not allow DNS queries to be answered with a local IP address. Why does this interfere with Pi-hole? DNS rebind is meant to be a countermeasure to an attack on your network. So in many cases, it's ac…

EDIT: ow and some AV software mangle DNS lookups:

Literally no ads being blocked

That Windows machine you are using wouldn't run a virus scanner like AVAST? AVAST offers a feature called RealSite that will inject additional DNS queries to a "trusted" DNS server (run by AVAST) in case something goes wrong with normal DNS resolution, see Hilfe: Windows löst Hostname auch ohne PiHole auf? - #26 by Chris80 (though German, it also contains a short solution description in English).

[RustedBuckett]

• Did all the commands for iptables, still nothing

[root@bucket ~]# sudo iptables -L -n
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

• Can't find any sort of rebind protection on my router, also looked through logs with nothing showing (TP-Link Archer VR600)
• No AV Software installed (Windows DF disabled also)

[deHakkelaar]

Whats IP and subnet on the Windows PC ?

netsh interface ipv4 show address

Do you have another client that can run those nslookups ?

[RustedBuckett]

C:\Users\Tom>netsh interface ip show address

Configuration for interface "Local Area Connection"
    DHCP enabled:                         Yes
    InterfaceMetric:                      6

Configuration for interface "Ethernet"
    DHCP enabled:                         Yes
    IP Address:                           192.168.1.100
    Subnet Prefix:                        192.168.1.0/24 (mask 255.255.255.0)
    Default Gateway:                      192.168.1.1
    Gateway Metric:                       0
    InterfaceMetric:                      25

Configuration for interface "Ethernet 3"
    DHCP enabled:                         Yes
    InterfaceMetric:                      25

Configuration for interface "Loopback Pseudo-Interface 1"
    DHCP enabled:                         No
    IP Address:                           127.0.0.1
    Subnet Prefix:                        127.0.0.0/8 (mask 255.0.0.0)
    InterfaceMetric:                      75

yep, got my laptop out and ran into nslookup timeouts

[deHakkelaar]

IP and subnet mask looks good.
Only thing between Pi-hole and your clients is the router.
Could assign a static IP on that laptop, connect the ethernet cable directly to Pi-hole without the router in between and run the lookups again.

[RustedBuckett]

Can you reword this i'm not sure I understand

-- connect the pi-hole directly to the laptop? the pi-hole is a laptop...so connect my laptop to the other laptop (pi-hole)??

[deHakkelaar]

On the laptop, change network settings from automatically acquiring IP details through DHCP into a static one:

And connect the ethernet cable connected to Pi-hole directly to the laptop without the router in between.
And run nslookups.

[RustedBuckett]

C:\Users\Home>nslookup google.com
Server:  UnKnown
Address:  fec0:0:0:ffff::1

*** UnKnown can't find google.com: No response from server

I think I did it right
Wifi disabled on laptop and just connected directly to pi-hole with static ip set
I then had wifi enabled on the pi-hole laptop

[deHakkelaar]

You cant do lookups for public domain names like google.com as Pi-hole isnt connected to internet anymore.
But if below one resolves, Pi-hole is working as expected:

nslookup pi.hole 192.168.1.101

And can conclude that the router is blocking something.
I dont have an answer for that so got to search the net or address TP-link support.

[RustedBuckett]

And to the surprise of nobody it dosen't work, just does a timeout like the rest of the other times
i wish this would just work

[deHakkelaar]

What does below show on the laptop after setting static IP ?

netsh interface ipv4 show address

And can you ping from that laptop:

ping 192.168.1.101

[RustedBuckett]

C:\Users\Home>netsh interface ipv4 show address

Configuration for interface "Ethernet"
    DHCP enabled:                         No
    IP Address:                           192.168.1.111
    Subnet Prefix:                        192.168.1.0/24 (mask 255.255.255.0)
    InterfaceMetric:                      5

Configuration for interface "Local Area Connection* 1"
    DHCP enabled:                         Yes
    InterfaceMetric:                      25

Configuration for interface "Local Area Connection* 10"
    DHCP enabled:                         Yes
    InterfaceMetric:                      25

Configuration for interface "Wi-Fi"
    DHCP enabled:                         Yes
    IP Address:                           192.168.1.124
    Subnet Prefix:                        192.168.1.0/24 (mask 255.255.255.0)
    Default Gateway:                      192.168.1.1
    Gateway Metric:                       0
    InterfaceMetric:                      50

Configuration for interface "Loopback Pseudo-Interface 1"
    DHCP enabled:                         No
    IP Address:                           127.0.0.1
    Subnet Prefix:                        127.0.0.0/8 (mask 255.0.0.0)
    InterfaceMetric:                      75

C:\Users\Home>ping 192.168.1.101

Pinging 192.168.1.101 with 32 bytes of data:
Reply from 192.168.1.101: bytes=32 time=1ms TTL=64
Reply from 192.168.1.101: bytes=32 time=1ms TTL=64
Reply from 192.168.1.101: bytes=32 time<1ms TTL=64
Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.101:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

[deHakkelaar]

Keep Wifi disabled while testing with nslookup.
Routes could go wrong otherwise.

[RustedBuckett]

Done. Same as above

[deHakkelaar]

Firewall on Pi-hole is still default accepting anything ?

sudo iptables -nL

I wonder if Selinux is messing up things.
What does below show on Pi-hole ?

getenforce

Might need sudo:

sudo getenforce