Help Us Beta Test FTLDNS

We disable the service with systemctl disable dnsmasq

As dnsmasq is embedded into FTL, there is no need to have it running separately :slight_smile:

1 Like

I'm on FTLDNS now. Update without obvious problems.

To monit users: adapt or deactivate your configuration file for previous dnsmasq.

2 posts were split to a new topic: Display of number of blocked entries

There is a typo with "dnsmsaq" instead of "dnsmasq"
"sudo systemctl status dnsmsaq" should be "sudo systemctl status dnsmasq"

2 Likes

Fixed it...

1 Like

5 posts were split to a new topic: IPv6 ICMP socket created fails

@koolkid1935 @Tntdruid Thanks for reporting, I will look into it.

Updated with the two commands above with 0 problems.
I'm on armbian 5.38 jessie (orange pi) with dnsmasq updated by hand to v2.76
At the moment it is working fine.

2 Likes

2 posts were split to a new topic: Unknown reply type in Query Log

Installed it on my RPi3 running Raspbian Stretch.
Both my Domain Controllers (simple home setup) use it as their only forwarder.
Normally it's the Pi-hole running in a CentOS VM.

No weird issues so far. Feels faster resolving wise, so that's good :slight_smile:

2 Likes

10 posts were split to a new topic: Unexpected version of dnsmasq on Raspbian Jessie

5 posts were split to a new topic: Fetching branches fails

3 posts were split to a new topic: Setting DNS cache limit with FTLDNS

4 posts were split to a new topic: Clients over time doesn’t update, just sits there with the spinnins

flawless!
works like a charm. have to play around with up and downgrade-procedure but.... nothin. :smile:
clean and small - like it!

3 Likes

So far the beta version works fine on my Pi.

It even solves the bug between dnsmasq < 2.78 and DNScrypt-proxy (see here), so I can use FTLDNS with DNSSec enabled on Pi side (which is not possible with the "master" branch), perfect !

2 Likes

2 posts were split to a new topic: pihole-FTL is working, but webmin says the service is not running

A post was split to a new topic: Lot of PTR queries

Will this new method support sending data to a system like ELK (Elastic, Logstash, Kibana) for further analysis? It sounded like there would not be logging like the past therefore less data available for ELK or Splunk.

Not a really important issue from the UI perspective - When you mouse over the Clients(over time) chart the pop up that displays the IP's get hidden if there are more than 3. A bit annoying that you cannot see the IP's that are causing issues since it's not sorted by high traffic IP