Hi,
I was using pi-hole in a proxmox docker environment just for the purpose of accessing one of my web servers in my lan as my router doesnt support nat hairspinning. Unfortunately this stopped working suddenly a week ago, i dont remember changing any settings but apparently i did something wrong? i tried to install unbound as it might help but as i am running in a docket environment i couldnt (it wanted to change some settings about ram) Anyways to sum it up, dns server in pihole is working but i cant access my websites through domain names as i used to, what can i do to troubleshot this thing. I changed some settings in dns settings rebooted pihole but nothing helped. Tried this both at linux and windows.
Thanks in advance
PS: when i ping one of my domains from command promt like ping abc.com it shows local ip like pinging 192.168.10.5 but it time outs
So it sounds like its resolving but not able to reach to machine?
From the linux machine what do you get if you dig one of the local domains?
What does dig pi.hole give you?
If it resolves what do you get with a traceroute to that ip?
Lastly you will want to post a debug log for the moderators / devs. You can do this from the piholes gui under tools section > generate debug log. Make sure to post the token.
When i traceroute to wan ip it return like this
traceroute to 94.55..(94.55..), 30 hops max, 60 byte packets
1 _gateway (192.168.10.1) 2.441 ms 2.895 ms 3.405 ms
2 94.55.. (94.55..) 0.390 ms 0.575 ms 0.644 ms
(i deleted some of my wan ip for privacy reasons)
When i traceroute to local ip of pi-hole it return like this
traceroute to 192.168.10.80 (192.168.10.80), 30 hops max, 60 byte packets
1 pi.hole (192.168.10.80) 0.312 ms 0.265 ms 0.251 ms
when i traceroute to local ip of any domains
traceroute to 192.168.10.5 (192.168.10.5), 30 hops max, 60 byte packets
1 * * *
2 * * *
when i traceroute any domains
traceroute to mydomaincom (192.168.10.5), 30 hops max, 60 byte packets
1 * * *
2 * * *
and so on
Am I correct in assuming you ran those from the pi itself?
This looks like a networking issue but I am confused as to why you can ping your gateway at 192.168.10.1 and your wan at 94..55.XX.XX but not a client at 192.168.10.5.
From the machine you ran those from, please post results from ip a
root@PiHole ~# traceroute 192.168.10.80
traceroute to 192.168.10.80 (192.168.10.80), 30 hops max, 60 byte packets
1 PiHole.lan (192.168.10.80) 0.311 ms 0.248 ms 0.232 ms
root@PiHole ~# traceroute mydomain.com
traceroute to mydomain.com (94.55..), 30 hops max, 60 byte packets
1 192.168.10.1 (192.168.10.1) 1.782 ms 2.201 ms 3.216 ms
2 94.55.. (94.55..) 0.420 ms 0.555 ms 0.618 ms
192.168.10.80 is pihole ip
192.168.10.5 is webserver ip which i cannot reach
94.55.. is my wan ip
Your initial post mentioned using Pihole in a docker container to access you local web servers. This docker interface doesn't look right to me BUT I have no docker experience so others are welcome to chime in.
Apologies but I'm out of ideas here, Dev shows pihole is ok. This seems like a proxmox / lxc issue of some kind. Its definitly network related. Perhaps someone else with proxmox experience can chime in. You may also want to ping the proxmox community as well. I wish I could help more.
i can access my websites when i am outside my network, also asked my friends and they can too, only problem i cant access my websites from inside my house when i connect to internet from my home ip. There arent any firewall rules in my router as it is a basic Asus ac68u, only 80 and 443 port forwards to webserver local ip and 2 routes to 2 vlans(my router has ip with 192.168.1.1 managed switch has two vlans with 192.168.10.1 and 192.168.20.1)
Hi,
Thank you for all your helps guys, with the help of a friend of mine who is a network engineer i figured it out it is a directadmin block issue. Apparently directadmin blocked my local ip. After removing my ip from blacklist everything started to work as expected.
