Has the issue with dnsmasq v<2.78 been resolved?


#1

This Year’s Febuary I upgraded pihole to version v3.3 ant FTL to v3.0 and came across the issue described later in pihole’s blog: https://pi-hole.net/2018/02/14/pi-hole-v3-3-released-its-extra-special/

I have pihole installed on Debian 8 Jessie (yes, Debian, it’s on VPS not on Raspberry Pi). Because the version of dnsmasq provided is 2.72 and doesn’t support log-queries=extra option I had to downgrade to version 3.2.1 and FTL 2.13.

Fast forward couple of months and I’m visiting pihole’s blog and github’s issues again. I see no mention about this issue being resolved, however I see the announcement of FTLDNS being developed: https://pi-hole.net/2018/02/22/coming-soon-ftldns-pi-holes-own-dns-dhcp-server/

My questions are:

  1. Can I safely upgrade my pi on debian 8? Has the issue with dnsmasq been resolved?
  2. If not, is the FTLDNS an option and how can I enable it? Do I have to git checkout to FTLDNS branch (https://github.com/pi-hole/FTL/tree/FTLDNS) and if so, which combination of versions of pihole, web and FTL should I choose?

#2

See this post for some workarounds for v3.3:

You could also update to the FTLDNS beta.


#3

Yeah, I’m aware of those options, they’re described in the blogpost as well.

How to do that? By git checkout or pihole -up?


#4

#5

So, to sum it up, there is no easy way to update. Either upgrade to stretch, manually pimp dnsmasq version or betatest FTLDNS branch. Thank you, will wait &see for the moment since all works fine with 3.2.1


#6

The last two options you said are both very easy; we even provide copy-paste instructions to perform them. The easiest is updating dnsmasq.


#7

It’s not about complexity, it’s about potential bugs. I run pihole on my production server and I don’t want to risk it to crash because of some potential dependency errors.


#8

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