Help Us Beta Test FTLDNS

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

When version 3.3 was released and all the issues starting to show up because of DNSMASQ ?

Basically the date of this Blog entry : Pi-hole v3.3 Released: It’s “Extra” Special – Pi-hole

I am runnig Jessie actually :wink:

Also have a Unify Controller running on it and everything works together just fine!

That's why you guys need to add FreeBSD support : No more silly Debian issues unless you switch to Ubuntu, which has it's own quirks and issues :wink:

Then consider using a different brand or a slightly larger one so it can spread the usage of it's cells :wink:

3 posts were split to a new topic: Auto logout of dashboard?

3 posts were split to a new topic: New privacy settings for FTLDNS

3 posts were split to a new topic: FTLDNS issues I have found

3 posts were split to a new topic: Checking out of branch fails with modified files

3 posts were split to a new topic: Using custom configuration with FTLDNS

2 posts were split to a new topic: Will FTLDNS kill my SD card?

7 posts were split to a new topic: Is dnsmasq future-proof enough for a project like Pi-hole?

Well, a combination of a Pi-hole application and an own DNS server sounds perfect.
Is that the meaning of FTLDNS ? Am I right ?

Will the external DNS providers like Google, the internet provider, Norton, etc be skipped and the router has to ask FTLDNS for the external traffic ?

Yes, exactly.

Nothing will be different from your current perspective because FTLDNS is just our fork of dnsmasq. So instead of installing dnsmasq, FTLDNS gets installed.

Your Pi-hole will contact whatever upstream DNS server you select, same as it always has.

2 posts were split to a new topic: BIND9 next to FTLDNS?

2 posts were split to a new topic: FTLDNS on Rock64?

7 posts were split to a new topic: FTLDNS in proxmox

Stay tuned for some exciting news about this to be released, soon.

edit See Add the ability to let Pi-Hole resolve DNS - #14 by DL6ER

1 Like

pihole + openvpn workz perfect - "jezuz - this FTL-thing is quick"
its time to donate......

p.s


the log looks good:
[2018-04-25 10:50:11.489] Notice: Increasing overTime struct size from 400 to 500 (788.61 KB)
[2018-04-25 15:52:44.864] ########## FTL started! ##########
[2018-04-25 15:52:44.864] FTL branch: FTLDNS
[2018-04-25 15:52:44.864] FTL version:
[2018-04-25 15:52:44.864] FTL commit: 3656ba2
[2018-04-25 15:52:44.864] FTL date: 2018-04-17 17:01:08 +0200
[2018-04-25 15:52:44.864] FTL user: pihole
[2018-04-25 15:52:44.864] Notice: Found no readable FTL config file
[2018-04-25 15:52:44.864] Using default settings
[2018-04-25 15:52:44.864] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
[2018-04-25 15:52:44.864] SOCKET_LISTENING: only local
[2018-04-25 15:52:44.864] AAAA_QUERY_ANALYSIS: Show AAAA queries
[2018-04-25 15:52:44.864] MAXDBDAYS: max age for stored queries is 365 days
[2018-04-25 15:52:44.864] RESOLVE_IPV6: Resolve IPv6 addresses
[2018-04-25 15:52:44.864] RESOLVE_IPV4: Resolve IPv4 addresses
[2018-04-25 15:52:44.864] DBINTERVAL: saving to DB file every minute
[2018-04-25 15:52:44.864] DBFILE: Using /etc/pihole/pihole-FTL.db
[2018-04-25 15:52:44.864] MAXLOGAGE: Importing up to 24.0 hours of log data
[2018-04-25 15:52:44.864] PRIVACYLEVEL: Set to 0
[2018-04-25 15:52:44.864] IGNORE_LOCALHOST: Show queries from localhost
[2018-04-25 15:52:44.864] Finished config file parsing
[2018-04-25 15:52:44.865] Database successfully initialized
[2018-04-25 15:52:44.865] Notice: Increasing queries struct size from 0 to 10000 (640.15 KB)
[2018-04-25 15:52:44.865] Notice: Increasing domains struct size from 0 to 1000 (672.15 KB)
[2018-04-25 15:52:44.865] Notice: Increasing clients struct size from 0 to 10 (672.47 KB)
[2018-04-25 15:52:44.865] Notice: Increasing forwarded struct size from 0 to 4 (672.66 KB)
[2018-04-25 15:52:44.865] New forward server: 149.112.112.112 (0/4)
[2018-04-25 15:52:44.865] Notice: Increasing overTime struct size from 0 to 100 (680.68 KB)
[2018-04-25 15:52:44.865] New forward server: 9.9.9.9 (1/4)
[2018-04-25 15:52:44.877] Notice: Increasing overTime struct size from 100 to 200 (704.60 KB)
[2018-04-25 15:52:44.894] Imported 7848 queries from the long-term database
[2018-04-25 15:52:44.894] -> Total DNS queries: 7848
[2018-04-25 15:52:44.894] -> Cached DNS queries: 2707
[2018-04-25 15:52:44.894] -> Forwarded DNS queries: 4344
[2018-04-25 15:52:44.894] -> Exactly blocked DNS queries: 797
[2018-04-25 15:52:44.894] -> Wildcard blocked DNS queries: 0
[2018-04-25 15:52:44.894] -> Unknown DNS queries: 0
[2018-04-25 15:52:44.894] -> Unique domains: 909
[2018-04-25 15:52:44.894] -> Unique clients: 3
[2018-04-25 15:52:44.894] -> Known forward destinations: 2
[2018-04-25 15:52:44.894] Successfully accessed setupVars.conf
[2018-04-25 15:52:44.896] Found no other running pihole-FTL process
[2018-04-25 15:52:44.904] PID of FTL process: 16411
[2018-04-25 15:52:44.904] Listening on port 4711 for incoming IPv4 telnet connections
[2018-04-25 15:52:44.904] Listening on port 4711 for incoming IPv6 telnet connections
[2018-04-25 15:52:44.904] Listening on Unix socket
[2018-04-25 15:52:44.905] Gravity list entries: 121666
[2018-04-25 15:52:44.905] No wildcard blocking list present
[2018-04-25 15:52:54.125] Gravity list entries: 121666
[2018-04-25 15:52:54.125] No wildcard blocking list present


could it be that i dont run web-ui ?

[SOLVED] update august '18

3 Likes

6 posts were split to a new topic: FTLDNS on Synology