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.
1 Like
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
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.
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
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
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
Keep Wifi disabled while testing with nslookup.
Routes could go wrong otherwise.
Done. Same as above
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
iptables still the same as above
getenforece is set to Disabled
Outa ideas other than install another distro like for example Debain.
Sorry 
1 Like
Thanks for trying dude really appreciate it, i'll install a different distro tomorrow and post the results 
1 Like
I installed Ubuntu and everything is working nicely no trouble whatsoever
Because I use a vpn (Express VPN) am I able to use a vpn for the pi-hole and also on the client (but dns settings changed on client to point to pi-hole)? Or will this not work?
Easiest would be to configure your router to act as the VPN client for E-VPN.
That way all traffic from your LAN would get routed through the tunnel.
And as the router can still push the Pi-hole DNS to its own clients via DHCP, you have both DNS via Pi-hole and traffic to/from internet via VPN.
But not all routers have that option.
If you let individual clients dial in, the VPN dialer will overide the DNS settings pushed by your router and configure E-VPN's own DNS servers on the client.
There are ways to use your own DNS servers while connected to VPN but you'll have to search the net or here for a solution.
1 Like
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.