Expected Behaviour:
When entering pi.hole/admin or pi.hole in any browser, the Web UI should come up. Furthermore, I should be able to enter customdomain.com and it should redirect the request to my local machine running my service, because I set customdomain.com to redirect to 192.168.1.147, where my service is hosted. I am using this to avoid a hairpin request, which my router can't handle and would otherwise hang.
My pi.hole is hosted on 192.168.1.165 on a raspberry pi 3 running raspbian. I have a server running on 192.168.1.147, forwarded to the public. I have a windows PC which I am using to send the requests.
Alternatively, I can enter 192.168.1.165/admin on the browser and it should open the Web UI.
Actual Behaviour:
I enter pi.hole on the URL and get a Server not found error. I enter customdomain.com and it hangs (as if it was requesting it from an outside DNS).
Entering 192.168.1.165 (or .../admin) works and lets me log into the webUI.
nslookup pi.hole returns server can't find pi.hole: NXDOMAIN.
nslookup pi.hole 192.168.1.165 returns
So correct.
curl -i http://pi.hole/admin/api.php returns Could not resolve host: pi.hole
I have (from the CLI):
- Flushed arp (network) tables
- restarted the DNS server
nslookup flurry.com returns a ton of addresses it found with 8.8.8.8
Please help me. Pihole has worked flawlessly for a week and a half 