3 posts were split to a new topic: Using custom configuration with FTLDNS
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.
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
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
Pihole works like a charm on my raspberry pi 3. I just updated to the FTLDNS Beta and everything is working on my raspberry pi except the query log. When I click it on the GUI it just show me the message: Processing. Tried rebooting the Pi but no luck.
See this related topic:
Thnx for the quick tip! I just reverted back to the master and then went for the FTLDNS beta again. Everything works now
I have added unbound to this and... it works! Now I see the "queries answered by" graph starting to populate with "localhost".
You can create or edit /etc/pihole/pihole-FTL.conf
and add IGNORE_LOCALHOST=yes
Then, restart FTL (sudo systemctl restart pihole-FTL
) and that will prevent localhost from showing in the query log.
After disable Query logging 'Query Log' will stop PI-hole complete