Server: 192.168.1.254
Address: 192.168.1.254#53
Non-authoritative answer:
Name: pi.hole
Address: 23.217.138.110
Name: pi.hole
Address: 23.202.231.169
This shows your client and Pi-hole are on different networks: 192.168.1.0/24 vs. 10.0.2.0/24.
They either have to be on the same network for Pi-hole to work, or your router has to supply routing between them while Pi-hole may need to listen to traffic on multiple interfaces.
It's also highly unusual that your current local DNS server at 192.168.1.254 (supposedly your router) resolves pi.hole to public IP addresses - that name should only be defined within your local network.
1 Like
So I would need to connect my pi hole machine to the same wifi as my client and reinstall?? I don't know how they are on different networks because I only have 1 router.
Running pihole -r with Reconfigure should be sufficient to make your Pi-hole aware of its new network environment.
Since you mention WiFi:
If you use a WiFi Access Point in your network, you may want to check that AP's configuration first and make sure you didn't explicitly configure that to create a separate network.
1 Like
After reconfiguring, pi-hole is still using 10.0.2.15 instead of my client ip. How do I fix this?? I am only connected to 1 wifi network.
I have no idea how your local network looks like.
These are basic networking issues - you'd have to get networking sorted on your side.
If your router is not handing out those 10.0.2.0/24 addresses, some network equipment like an AP may, or a WiFi powerline extension, or, or ,or...
You may also run Pi-hole in some kind of virtualisation environment, in which case you'd have to configure network integration with your virtualisation host.
1 Like
I just changed my pi hole's ip to 75.60.120.239. Now when I go to http://75.60.120.239/admin/, I get connection refused. After running nslookup pi.hole I got:
Server: 192.168.1.254
Address: 192.168.1.254#53
Non-authoritative answer:
Name: Pi.Hole
Address: 23.202.231.169
Name: Pi.Hole
Address: 23.217.138.110
That is a public IP address.
You should only use it if you own it, and you shouldn't use it as an address for Pi-hole in your local network.
1 Like
Sorry for all the dumb questions, but how do I find my private ip address??
Your DHCP server assigns private IP addresses.
Most commonly, routers and access points will act as a DHCP server.
To solve your issue, you'd have to find the instance that is assigning IPs from the 10.0.2.0/24 range.
According to your debug log, that's likely the device living at 10.0.2.2.
EDIT: A guess: Your router wouldn't offer a guest network on that separate IP range?
1 Like
No, my router does not offer a guest network. After running ifconfig I get:
enp1s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 54:bf:64:34:4a:fe txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 15123 bytes 1549857 (1.5 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 15123 bytes 1549857 (1.5 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 75.60.120.239 netmask 255.255.252.0 broadcast 75.60.123.255
inet6 fe80::341c:9269:532f:247c prefixlen 64 scopeid 0x20<link>
ether 30:24:32:ba:9e:01 txqueuelen 1000 (Ethernet)
RX packets 7236971 bytes 10344146353 (10.3 GB)
RX errors 0 dropped 87 overruns 0 frame 0
TX packets 631310 bytes 85386561 (85.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
So my private ip would be 127.0.0.1 right?? And what would be my default gateway??
No.
That is the loopback address - virtually any device running a TCP/IP stack has that.
I've linked information on private addresses above - have a read to learn which address ranges you should see. Both your client's and your Pi-hole machine's previous address were on (separate) private address ranges.
You have somehow misconfigured your network - the only device with a public IPv4 address should be your router/modem.
Your Pi-hole should not have a public IPv4 address at all if run on a machine in your local network.
I repeat:
These are basic networking issues - you'd have to get networking sorted on your side.
So far, you claim your router is the only dedicated networking equipment in your local network.
This would mean your router is handing out IPv4 addresses from the 192.168.1.0/24 as well as 10.0.2.0/24 ranges, so there must be an option in your router to control this, and you'd have to find out what would make your client to join one network or the other.
If your router is not handing out those 10.0.2.0/24 addresses, some network equipment like an Access Point may, or a WiFi powerline extension, or a wireless range extender, or ,or...
If you do not run any additional network equipment apart from your router, you may run Pi-hole in some kind of virtualisation environment, in which case you'd have to configure network integration with your virtualisation host.
1 Like
Thanks for the information you gave me, I've fixed my network problem. Now my admin page is working great. Sorry if I asked any dumb questions.
Glad you got things sorted 
Those weren't dumb questions, and you've come to the right place asking them - lending support or patching up knowlegde gaps is among the most preeminent reasons for this forum to exist.
It's just that the expertise that this forums can offer (including me, who knows a lot less than the forum users combined) is somewhat focussed on Pi-hole issues, so we can at best point you in the right direction if you face other issues not directly related to Pi-hole.
Good thing that worked for you.
For the sake of other users who might have similar issues, would you be able to describe how you finally solved it?
Also, knowing your router's make and model might help, if problem or solution somehow are linked to it.
1 Like
I was running my pihole on a virtual machine, so I had to change my network settings on the virtual box so my network would recognize it as a computer.
One last question though : How do I add multiple domains to the black list at a time?? Is this a feature in pi-hole?? I would like to block these domains : https://gist.githubusercontent.com/anudeepND/adac7982307fec6ee23605e281a57f1a/raw/5b8582b906a9497624c3f3187a49ebc23a9cf2fb/Test.txt
Copy the lot of them from the web page to your clipboard, and paste the contents of the clipboard into Admin GUI > Group Management > domains > Domain window, the select Add to Blacklist.
I will note that these won't block YouTube ads as you expect, and will likely break YouTube functionality.
1 Like
Nevermind then. Thanks for the answer.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.