Blocked domain resolves as 127.0.0.1 instead of public IPv4

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

Expected Behaviour:

Latest PiHole installation via the one step installer process on a CentOS Linux release 7.9.2009 box. Blocklist works as expected for the default mode.

Actual Behaviour:

However, when using the IP or IP-NODATA-AAAA modes, the blocked domains get resolved as ::1 or 127.0.0.1 instead of using the public IPv6 or IPv4 address defined in the /etc/pihole/setupVars.conf file:

PIHOLE_INTERFACE=ens2f1
IPV4_ADDRESS=110.111.222.18/27
IPV6_ADDRESS=2345:cd00::18

I then came across Automate IP blocking mode by DL6ER · Pull Request #965 · pi-hole/FTL · GitHub as well.

dig A 2bdfb.spinakrosa.at +short at 110.111.222.18 would return 127.0.0.1 instead of the expected 110.111.222.18. However, dig A 2bdfb.spinakrosa.at +short at 2345:cd00::18 would return the IPv4 address 110.111.222.18 instead of the localhost IP. Not sure what's causing this strange behaviour.

Adding these two entries (IP address is deliberately mistyped) into the pihole-FTL.conf file and restarting pihole seems to have fixed the issue:
REPLY_ADDR4=xxx.abc.123.123
REPLY_ADDR6=12:12:12::1

Debug Token:

https://tricorder.pi-hole.net/gGD8zVlc/

A public facing DNS server likely violates the terms and conditions of your ISP or hosting solution. We at the Pi-hole project do not in any circumstance recommend, condone, or support public facing DNS with the project. However, at the IP address you provided above,

such a open resolver is found. There exist several open ports at this IP address. When visiting it, I'm redirected to a page with an expires HTTPS certificate where it offers me a Sikka broadband SBPL IP Manager.
There is no appropriate protection in place and I was able to read that you're using Pi-hole FTL 5.8.1 with privacy level 0 (i.e., show everything). I stopped right here, however, I could have extracted a lot more information (used DNS servers, statistics, etc.).

There are far too many ways someone can use it in a DNS based attack.

Companies like CF, OpenDNS, and Google have millions of dollars invested in their DNS server infrastructure to prevent this you as a one off user do not.

The recommended course of action for PERSONAL use is to use a VPN to allow use of pi-hole outside of the LAN there is a very well written guide located here

We do support non-personal use however it is on a case by case basis and should be directed towards the contact us page on https://pi-hole.net We're glad to give support/help if your issue turns out to be no mistake and not a harmful open resolver.

One interesting example of open resolver abuse for DoS attacks that was linked here before: https://www.ncsc.gov.ie/emailsfrom/DDoS/DNS/

Hi, thanks for the response and concern. I am getting those addressed straight away. No one wants a harmful open resolver.. :slight_smile:

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