Please follow the below template, it will help us to help you!
Please ensure that you are running the latest version of the beta code. Run pihole -up to update to the latest, then verify that the problem still exists before reporting it.
Problem with Beta 5.0:
pi@raspberrypi:~ $ pihole -up
[i] Checking for updates...
[i] Pi-hole Core: up to date
[i] Web Interface: up to date
[i] FTL: up to date
[i] Warning: You are using FTL from a custom branch (release/v5.0) and might be missing future releases.
[✓] Everything is up to date!
pi@raspberrypi:~ $ dig chaos txt version.bind +short "dnsmasq-2.78"
its saying everything is up to date but, I'm on an old dnsmasq.... how can I fix this
This is showing the correct version of dnsmasq running. One of the developers will have to weigh in with where the incorrect information is coming from.
That is OK, assuming you want the Pi to use the router for DNS resolution. It appears that your router is running that version of dnsmasq that was reported.
apparently, there is at least one blocklist that blocks version.bind
pihole -q version.bind
Match found in https://raw.githubusercontent.com/DandelionSprout/adfilt/master/Alternate%20versions%20Anti-Malware%20List/AntiMalwareHosts.txt:
version.bind
In order for the version check to work, you need to whitelist version.bind, or you'll get something like:
At the risk of veering this thread off topic - if you subscribe to dodgy lists, you get dodgy results.
Whomever maintains that list has some misconceptions of how a domain blocker works, based on this opening statement:
my list hereby claims to remove more than 25% of all known malware sites with just a 2-digit amount of entries. This is mostly done by blocking top-level domains that have become devastatingly abused by spammers, usually because they allowed for free and uncontrolled domain registrations
A hosts based domain blocker won't block entire top-level domains - it only blocks a specific domain.
About a dozen entries with IP's, not domain names. If you have the IP, you won't be requesting the IP from a DNS server.
127.0.0.1 54.209.22.226
And, as you noted:
If you run a webserver of any sort, and you get incoming requests to resolve these domains, that's rarely a good sign for that requestor's intentions
I have, and probably many users , been using the firebog lists. Personally I use the Non-crossed lists (For when someone is usually around to whitelist falsely blocked sites).
