Pihole DNS No Internet/Web Interface Not Working Outside VM

Help
1

Please follow the below template, it will help us to help you!

Expected Behaviour:

Pihole running and blocking ads, web interface reachable

Actual Behaviour:

After replacing router DNS from auto to Pihole DNS, devices report "connected, no internet" and web interface at either pi.hole/admin or "1.1.1.1"/admin don't work

pi.hole/admin error: pi.hole's server IP address could not be found
"1.1.1.1"/admin error: took too long to respond, or refused to connect

These issues don't appear on the VM

Debug Token:

u45jwzcra6

Set pihole up in VMware running Ubuntu 16.04, installation ran successfully, changed DNS to given number post installation, after saving changes on router settings devices report no internet when connected to network. Attempting to go to web interface via pi.hole/admin or ip/admin results in error.

Attempting to use the internet/the Pihole web interface on the VM itself works fine, ads are blocked and the interface is reachable.

4

let's start with the funky one ...

1.1.1.1 is actually a running DNS service (a public IP) and you will never be able to access it since it belongs to Cloudflare:

https://1.1.1.1/

Based on your debug log, you would access the admin interface from outside the VM with http://172.16.36.128/admin

That will work only if you have port 80 open in the VM environment.

Also, DNS requests require port 53.

If you want to use the visualized Pi-hole as your DNS, you need to make sure that port 53 in your VM is also accessible from outside the virtual environment,

5

Sorry, that was confusing, I put 1.1.1.1 as a placeholder, I was trying to access it using http://172.16.36.128/admin when getting the error

Working on the port opening, unfortunately VMware doesn't have super clear instructions on how to do that

You wouldn't happen to have any idea where to look, would you?

6

It probably resides under your firewall settings, on your VM OS.

7

Ok so from my understanding, I've updated the firewall to include rules to allow incoming connections to ports 80 and 53. Prior to this, the firewall wasn't active at all, by default

If the ports were successfully opened, I should be able to log in to the web interface via the ip/admin, right?

8

You'd have to find out why the requests are not hitting your VM environment.

Pi-hole sounds like it's working as expected, within the VM.

1 Like
9

Yeah, not sure how though. I'm almost positive I have ports 80 and 53 open now, pihole seems to be running dns services (both marked LISTEN under the firewall) and I've opened 80 and 53 on both tcp/udp from anywhere, as well as the pihole ip specifically. Still no dice

10

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