gpb
March 27, 2020, 4:31pm
28
I used "pihole checkout web new/all_clients_network_table" several days ago when it was made available and haven't changed since. Is there a command I can issue to check what my current branch is? OK...so I'm confused...lol. Which should I be on for it to work as we were discussing?
Pi-hole version is v4.3.5-450-g1b35eeb (Latest: v4.4)
AdminLTE version is v4.3.2-437-gbc9c656e (Latest: v4.3.3)
FTL version is vDev-7759a76 (Latest: v4.3.1)
You can check your current branch in the footer of the WEB GUI or on github by looking for the commit ('7759a76'). But I know 7759a76 is pihole checkout web new/all_clients_network_table
If it's working for you it is fine and you don't have to do anything. But if you want to help further debugging you could do the steps I have mentioned here .
gpb
March 27, 2020, 4:46pm
30
Thanks...switched to "no_auto".
DL6ER
March 27, 2020, 5:25pm
31
Just for the future: pihole-FTL branch
Yes. I thought for a second about an option where users can say: Yes, my DHCP server ensures that the same devices always get the same IP addresses, but, hey, most users wouldn't know probably and we should not go this far. We are already much farther than I planed to go, initially.
The important question at this point seems to be: Why are you seeing incomplete
devices at all . I did never see such, however, I, apparently, also do not own fancy enough devices to trigger this. Normal computers and laptops behave ... well .. normally. A once-and-for-all solution seems to be to switch to Pi-hole's DHCP server because the ARP table should then be guaranteed to have the maximum available wisdom in your network. Just saying.
No, they don't conflict. The transformation rule can always only come on top of an already added mock-device. And this would not have been added if there would have been an incomplete
record. So there has had to be no entry for this device at all in the ARP table, at least once when we checked.
The rules are already quite complex now and I wouldn't want to push their complexity further, I'm going to document them now in the source code to ensure we all understand them at some distant point in the future where we look at this again.
gpb
March 27, 2020, 5:39pm
32
@DL6ER I don't mind the duplicates, I understand the issue. I think it's excellent as is and appreciate the effort and glad I was able to help with feedback. I prefer to have the DHCP servers on the router (OPNsense) since it controls VLANs and for a while a second physical LAN. And I have other reporting utilities running on the router box that also grab dhcp data and prefer not to introduce additional complexity on that device. Thx!
Thanks
Thanks for the explanation. I think I got confused by your suggestion.
I’ve seen you have also be reading on the other discussion, I’m wondering if we should now undo the non-adding of the incomplete
or failed
devices? It should now be fine to add them as mock-devices as FTL can now convert them into “real” devices once more ARP data arrives (at least if it arrives within one hour after the mock device was created, we can tweak this timeout)
DL6ER
March 27, 2020, 6:43pm
34
Yeah, not done, indeed just a suggestion. There is no harm in keeping both, just somewhat higher added complexity of the code.
1 Like
For me, none of my local hostnames get resolved in the "Top Clients (total)" table of the Dashboard.
Pihole is not my DHCP. I can resolve the IPs to hostnames on the pihole using dig and pointing it to my router/DHCP server. I have "Conditional Forwarding" enabled and added the IP of my router and the local domain name (local.mydomain.de). Example given below:
19:10:52 [~]
root@pihole $ dig -x 10.0.1.89 @10.0.0.254
; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> -x 10.0.1.89 @10.0.0.254
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21542
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;89.1.0.10.in-addr.arpa. IN PTR
;; ANSWER SECTION:
89.1.0.10.in-addr.arpa. 0 IN PTR x1.local.mydomain.de.
;; Query time: 1 msec
;; SERVER: 10.0.0.254#53(10.0.0.254)
;; WHEN: Tue Apr 07 19:12:30 CEST 2020
;; MSG SIZE rcvd: 85
19:12:30 [~]
root@pihole $ dig -x 10.0.1.89 @localhost
; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> -x 10.0.1.89 @localhost
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54050
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;89.1.0.10.in-addr.arpa. IN PTR
;; Query time: 2 msec
;; SERVER: ::1#53(::1)
;; WHEN: Tue Apr 07 19:12:35 CEST 2020
;; MSG SIZE rcvd: 51
Any ideas where to start looking for the problem?
Cheers,
Bjoern
gpb
April 7, 2020, 5:28pm
36
Did you flush your network table from the settings screen?
Hej,
yes, multiple times, restarted, etc... nothing helped
Cheers,
Bjoern
DL6ER
April 8, 2020, 9:00am
38
Conditional Forwarding is something that has been there since the very early days of Pi-hole. Unfortunately, it isn't the most reliable thing you can imagine.
Try disabling it and adding instead
rev-server=10.0.0.0/8,10.0.0.254
to a new file
/etc/dnsmasq.d/05-rev-server.conf
and run
pihole restartdns
This will make sure to send all PTRs for 10.*.*.*
names to your router's IP address.
Fingers crossed that the hostnames will show up a few minutes later.
Hej, thanks for helping!
Disabling "conditional forwarding" and adding your suggestion at least fixed "dig" instantly after restarting DNS:
root@pihole $ dig -x 10.0.1.89 @10.0.0.254
; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> -x 10.0.1.89 @10.0.0.254
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5657
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;89.1.0.10.in-addr.arpa. IN PTR
;; ANSWER SECTION:
89.1.0.10.in-addr.arpa. 0 IN PTR x1.local.mydomain.de.
;; Query time: 1 msec
;; SERVER: 10.0.0.254#53(10.0.0.254)
;; WHEN: Wed Apr 08 11:18:24 CEST 2020
;; MSG SIZE rcvd: 85
root@pihole $ dig -x 10.0.1.89 @localhost
; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> -x 10.0.1.89 @localhost
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59417
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;89.1.0.10.in-addr.arpa. IN PTR
;; ANSWER SECTION:
89.1.0.10.in-addr.arpa. 0 IN PTR x1.local.mydomain.de.
;; Query time: 2 msec
;; SERVER: ::1#53(::1)
;; WHEN: Wed Apr 08 11:18:30 CEST 2020
;; MSG SIZE rcvd: 85
But even after flushing logs, and the network table followed by a reboot, the hostnames do not show up on the dashboard:
Even after waiting for 41 min (292 requests later for 10.0.1.89), no hostnames show up on the dashboard.
Cheers,
Bjoern
Verify that Never forward reverse lookups for private IP ranges is unchecked on Pi-hole’s Settings | DNS panel.
(Edit: It wouldn't normally interfere with Conditional Forwarding , so just a guess. But needs to be unchecked if you want local hostname resolution when using your router as Pi-hole's sole upstream without CF enabled.)
It was indeed active, but unchecking it didn't help (flushed everything and restarted DNS)
The hostnames are still not showing up.
How did you specify that?
Normally, your router would decide on a local domain name, and not every router model does allow changing it.
Can you verify your local domain name in your router?
Alternatively, on a Windows machine it would show up as DNS suffix in ipconfig /all
.
On Linux with installed nmap
, you may use sudo nmap --script broadcast-dhcp-discover
and look for Domain Name . On a machine with multiple network interfaces, you may need to additionally specify an interface with that (e.g. by adding -e eth0
).
Or use sudo dhcpcd -T | grep "domain_name"
if dhcpcd
is active.
Hej,
here is the output of the Laptop (x1 - 10.0.1.89):
`PS C:\Users\conta> ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : x1
Primary Dns Suffix . . . . . . . : local.mydomain.de
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : local.mydomain.de`
This is the output of nmap:
13:18:22 [~]
root@openhab $ nmap --script broadcast-dhcp-discover
Starting Nmap 7.70 ( https://nmap.org ) at 2020-04-08 13:18 CEST
Pre-scan script results:
| broadcast-dhcp-discover:
| Response 1 of 1:
| IP Offered: 10.0.1.92
| DHCP Message Type: DHCPOFFER
| Server Identifier: 10.0.0.254
| IP Address Lease Time: 5m00s
| Subnet Mask: 255.255.254.0
| Router: 10.0.0.254
| Domain Name Server: 10.0.0.2
| Domain Name: local.mydomain.de
| Renewal Time Value: 2m30s
|_ Rebinding Time Value: 4m22s
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 2.40 seconds
10.0.0.2 is pihole
10.0.0.254 is the USG 3P router
And here is a screenshot from my UniFi USG 3P router. The domain-name is set to local.mydomain.de:
bolausson:
UniFi USG 3P router.
I know Ubiquiti devices to be tricky with local hostnames unless dnsmasq
is enabled on them, but that would normally exhibit a failing reverse dig
as well. And yours seems to work.
I am out of ideas as to what's causing your issue.
You may try setting up your router as Pi-hole's sole upstream - with Never forward reverse lookups for private IP ranges unchecked - instead of using Conditional Forwarding , but will then have to control final upstream DNS through your router's settings.
DL6ER
April 8, 2020, 11:51am
45
This should be sufficient to get hostname resolution on the dashboard.
Please add
DEBUG_API=true
to /etc/pihole/pihole-FTL.conf
(create if it does not exist, you may need sudo
-powers) and run
pihole restartdns
After a while, you should see lines like Trying to resolve XYZ
in /var/log/pihole-FTL.log
.
How do they look like exactly?
Here you go:
[2020-04-08 17:56:59.743 872] *****************************
[2020-04-08 17:56:59.743 872] * Debugging enabled *
[2020-04-08 17:56:59.743 872] * DEBUG_DATABASE NO *
[2020-04-08 17:56:59.743 872] * DEBUG_NETWORKING NO *
[2020-04-08 17:56:59.743 872] * DEBUG_LOCKS NO *
[2020-04-08 17:56:59.743 872] * DEBUG_QUERIES NO *
[2020-04-08 17:56:59.743 872] * DEBUG_FLAGS NO *
[2020-04-08 17:56:59.743 872] * DEBUG_SHMEM NO *
[2020-04-08 17:56:59.743 872] * DEBUG_GC NO *
[2020-04-08 17:56:59.743 872] * DEBUG_ARP NO *
[2020-04-08 17:56:59.743 872] * DEBUG_REGEX NO *
[2020-04-08 17:56:59.743 872] * DEBUG_API YES *
[2020-04-08 17:56:59.743 872] * DEBUG_OVERTIME NO *
[2020-04-08 17:56:59.743 872] * DEBUG_EXTBLOCKED NO *
[2020-04-08 17:56:59.743 872] * DEBUG_CAPS NO *
[2020-04-08 17:56:59.743 872] * DEBUG_DNSMASQ_LINES NO *
[2020-04-08 17:56:59.743 872] * DEBUG_VECTORS NO *
[2020-04-08 17:56:59.743 872] *****************************
[2020-04-08 17:56:59.831 872] INFO: No regex whitelist entries found
[2020-04-08 17:56:59.841 872] Compiled 0 whitelist and 5 blacklist regex filters in 29.5 msec
[2020-04-08 17:57:00.315 872] Trying to resolve 10.0.0.1
[2020-04-08 17:57:00.329 872] Trying to resolve 10.0.1.89
[2020-04-08 17:57:00.342 872] Trying to resolve 10.0.0.116
[2020-04-08 17:57:00.355 872] Trying to resolve 10.0.1.5
[2020-04-08 17:57:00.368 872] Trying to resolve 10.0.1.64
[2020-04-08 17:57:00.380 872] Trying to resolve 10.0.1.65
[2020-04-08 17:57:00.393 872] Trying to resolve ::1
[2020-04-08 17:57:00.393 872] 7 / 7 client host names resolved
[2020-04-08 17:57:00.393 872] Trying to resolve 10.0.0.254
[2020-04-08 17:57:00.406 872] 1 / 1 upstream server host names resolved
[2020-04-08 17:58:01.320 872] Trying to resolve 10.0.1.44
[2020-04-08 17:58:01.426 872] Trying to resolve 10.0.1.19
[2020-04-08 17:58:01.438 872] 2 / 9 client host names resolved
[2020-04-08 17:58:01.439 872] 0 / 1 upstream server host names resolved
[2020-04-08 17:58:16.672 872] New upstream server: 127.0.0.1 (1/1024)
----------------------------------------------------------------------------------------------------------------2020/04/08 17:58:59----------------------------------------------------------------------------------------------------------------
[2020-04-08 17:59:00.000 872] Trying to resolve 10.0.1.67
[2020-04-08 17:59:00.121 872] 1 / 10 client host names resolved
[2020-04-08 17:59:00.121 872] Trying to resolve 127.0.0.1
[2020-04-08 17:59:00.121 872] 1 / 2 upstream server host names resolved
[2020-04-08 18:00:00.198 872] 0 / 10 client host names resolved
[2020-04-08 18:00:00.198 872] 0 / 2 upstream server host names resolved
[2020-04-08 18:00:00.703 872] Trying to resolve 10.0.0.1
[2020-04-08 18:00:00.717 872] Trying to resolve 10.0.1.89
[2020-04-08 18:00:00.731 872] Trying to resolve 10.0.0.116
[2020-04-08 18:00:00.744 872] Trying to resolve 10.0.1.5
[2020-04-08 18:00:00.758 872] Trying to resolve 10.0.1.64
[2020-04-08 18:00:00.771 872] Trying to resolve 10.0.1.65
[2020-04-08 18:00:00.785 872] Trying to resolve ::1
[2020-04-08 18:00:00.785 872] Trying to resolve 10.0.1.44
[2020-04-08 18:00:00.799 872] Trying to resolve 10.0.1.19
[2020-04-08 18:00:00.817 872] Trying to resolve 10.0.1.67
[2020-04-08 18:00:00.830 872] 10 / 10 client host names resolved
[2020-04-08 18:00:00.830 872] Trying to resolve 10.0.0.254
[2020-04-08 18:00:00.844 872] Trying to resolve 127.0.0.1
[2020-04-08 18:00:00.845 872] 2 / 2 upstream server host names resolved
----------------------------------------------------------------------------------------------------------------2020/04/08 18:00:40----------------------------------------------------------------------------------------------------------------
[2020-04-08 18:01:00.409 872] 0 / 10 client host names resolved
[2020-04-08 18:01:00.409 872] 0 / 2 upstream server host names resolved
From another thread I stole the idea to switch to another FTL branch
pihole checkout ftl tweak/more_resolver_debugging
Looks like all local IP addresses are resolved to
"" (N/A)
I did setup DNS-Over-HTTPS as described here: Redirecting...
Does this interfere?
Herer is the output:
[2020-04-08 21:01:15.463 26687] Using log file /var/log/pihole-FTL.log
[2020-04-08 21:01:15.463 26687] ########## FTL started! ##########
[2020-04-08 21:01:15.463 26687] FTL branch: tweak/more_resolver_debugging
[2020-04-08 21:01:15.463 26687] FTL version: vDev-bd5749d
[2020-04-08 21:01:15.463 26687] FTL commit: bd5749d
[2020-04-08 21:01:15.463 26687] FTL date: 2020-04-08 15:10:57 +0200
[2020-04-08 21:01:15.463 26687] FTL user: pihole
[2020-04-08 21:01:15.463 26687] Compiled for armhf (compiled on CI) using arm-linux-gnueabihf-gcc (Debian 6.3.0-18) 6.3.0 20170516
[2020-04-08 21:01:15.463 26687] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
[2020-04-08 21:01:15.464 26687] SOCKET_LISTENING: only local
[2020-04-08 21:01:15.464 26687] AAAA_QUERY_ANALYSIS: Show AAAA queries
[2020-04-08 21:01:15.464 26687] MAXDBDAYS: max age for stored queries is 365 days
[2020-04-08 21:01:15.464 26687] RESOLVE_IPV6: Resolve IPv6 addresses
[2020-04-08 21:01:15.464 26687] RESOLVE_IPV4: Resolve IPv4 addresses
[2020-04-08 21:01:15.464 26687] DBINTERVAL: saving to DB file every minute
[2020-04-08 21:01:15.464 26687] DBFILE: Using /etc/pihole/pihole-FTL.db
[2020-04-08 21:01:15.464 26687] MAXLOGAGE: Importing up to 24.0 hours of log data
[2020-04-08 21:01:15.464 26687] PRIVACYLEVEL: Set to 0
[2020-04-08 21:01:15.464 26687] IGNORE_LOCALHOST: Show queries from localhost
[2020-04-08 21:01:15.464 26687] BLOCKINGMODE: Null IPs for blocked domains
[2020-04-08 21:01:15.464 26687] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
[2020-04-08 21:01:15.464 26687] DBIMPORT: Importing history from database
[2020-04-08 21:01:15.464 26687] PIDFILE: Using /var/run/pihole-FTL.pid
[2020-04-08 21:01:15.464 26687] PORTFILE: Using /var/run/pihole-FTL.port
[2020-04-08 21:01:15.464 26687] SOCKETFILE: Using /var/run/pihole/FTL.sock
[2020-04-08 21:01:15.464 26687] SETUPVARSFILE: Using /etc/pihole/setupVars.conf
[2020-04-08 21:01:15.464 26687] MACVENDORDB: Using /etc/pihole/macvendor.db
[2020-04-08 21:01:15.464 26687] GRAVITYDB: Using /etc/pihole/gravity.db
[2020-04-08 21:01:15.465 26687] PARSE_ARP_CACHE: Active
[2020-04-08 21:01:15.465 26687] REGEX_IGNORECASE: Disabled. Regex is case sensitive
[2020-04-08 21:01:15.465 26687] CNAME_DEEP_INSPECT: Active
[2020-04-08 21:01:15.465 26687] DELAY_STARTUP: No delay requested.
[2020-04-08 21:01:15.465 26687] FORCE_FIRST_RESOLVER: Inactive
[2020-04-08 21:01:15.465 26687] *****************************
[2020-04-08 21:01:15.465 26687] * Debugging enabled *
[2020-04-08 21:01:15.465 26687] * DEBUG_DATABASE NO *
[2020-04-08 21:01:15.465 26687] * DEBUG_NETWORKING NO *
[2020-04-08 21:01:15.465 26687] * DEBUG_LOCKS NO *
[2020-04-08 21:01:15.465 26687] * DEBUG_QUERIES NO *
[2020-04-08 21:01:15.465 26687] * DEBUG_FLAGS NO *
[2020-04-08 21:01:15.465 26687] * DEBUG_SHMEM NO *
[2020-04-08 21:01:15.465 26687] * DEBUG_GC NO *
[2020-04-08 21:01:15.465 26687] * DEBUG_ARP NO *
[2020-04-08 21:01:15.465 26687] * DEBUG_REGEX NO *
[2020-04-08 21:01:15.465 26687] * DEBUG_API YES *
[2020-04-08 21:01:15.465 26687] * DEBUG_OVERTIME NO *
[2020-04-08 21:01:15.465 26687] * DEBUG_EXTBLOCKED NO *
[2020-04-08 21:01:15.465 26687] * DEBUG_CAPS NO *
[2020-04-08 21:01:15.465 26687] * DEBUG_DNSMASQ_LINES NO *
[2020-04-08 21:01:15.466 26687] * DEBUG_VECTORS NO *
[2020-04-08 21:01:15.466 26687] *****************************
[2020-04-08 21:01:15.466 26687] Finished config file parsing
[2020-04-08 21:01:15.467 26687] Database version is 5
[2020-04-08 21:01:15.467 26687] Database successfully initialized
[2020-04-08 21:01:15.468 26687] New upstream server: 10.0.0.254 (0/1024)
[2020-04-08 21:01:15.469 26687] New upstream server: 127.0.0.1 (1/1024)
[2020-04-08 21:01:15.489 26687] Resizing "/FTL-strings" from 4096 to 8192
[2020-04-08 21:01:15.504 26687] Resizing "/FTL-queries" from 229376 to 458752
[2020-04-08 21:01:15.520 26687] Resizing "/FTL-strings" from 8192 to 12288
[2020-04-08 21:01:15.522 26687] Imported 5505 queries from the long-term database
[2020-04-08 21:01:15.523 26687] -> Total DNS queries: 5505
[2020-04-08 21:01:15.523 26687] -> Cached DNS queries: 817
[2020-04-08 21:01:15.523 26687] -> Forwarded DNS queries: 2314
[2020-04-08 21:01:15.523 26687] -> Blocked DNS queries: 2374
[2020-04-08 21:01:15.523 26687] -> Unknown DNS queries: 0
[2020-04-08 21:01:15.523 26687] -> Unique domains: 349
[2020-04-08 21:01:15.523 26687] -> Unique clients: 15
[2020-04-08 21:01:15.523 26687] -> Known forward destinations: 2
[2020-04-08 21:01:15.523 26687] Successfully accessed setupVars.conf
[2020-04-08 21:01:15.523 26687] DEBUG: argv[0] = ""
[2020-04-08 21:01:15.523 26687] DEBUG: argv[1] = "-k"
[2020-04-08 21:01:15.528 26689] PID of FTL process: 26689
[2020-04-08 21:01:15.528 26689] Listening on port 4711 for incoming IPv4 telnet connections
[2020-04-08 21:01:15.529 26689] Listening on port 4711 for incoming IPv6 telnet connections
[2020-04-08 21:01:15.529 26689] Listening on Unix socket
[2020-04-08 21:01:15.532 26689] Reloading DNS cache
[2020-04-08 21:01:15.532 26689] Blocking status is enabled
[2020-04-08 21:01:15.532 26689] *****************************
[2020-04-08 21:01:15.532 26689] * Debugging enabled *
[2020-04-08 21:01:15.532 26689] * DEBUG_DATABASE NO *
[2020-04-08 21:01:15.532 26689] * DEBUG_NETWORKING NO *
[2020-04-08 21:01:15.532 26689] * DEBUG_LOCKS NO *
[2020-04-08 21:01:15.532 26689] * DEBUG_QUERIES NO *
[2020-04-08 21:01:15.532 26689] * DEBUG_FLAGS NO *
[2020-04-08 21:01:15.532 26689] * DEBUG_SHMEM NO *
[2020-04-08 21:01:15.533 26689] * DEBUG_GC NO *
[2020-04-08 21:01:15.533 26689] * DEBUG_ARP NO *
[2020-04-08 21:01:15.533 26689] * DEBUG_REGEX NO *
[2020-04-08 21:01:15.533 26689] * DEBUG_API YES *
[2020-04-08 21:01:15.533 26689] * DEBUG_OVERTIME NO *
[2020-04-08 21:01:15.533 26689] * DEBUG_EXTBLOCKED NO *
[2020-04-08 21:01:15.533 26689] * DEBUG_CAPS NO *
[2020-04-08 21:01:15.533 26689] * DEBUG_DNSMASQ_LINES NO *
[2020-04-08 21:01:15.533 26689] * DEBUG_VECTORS NO *
[2020-04-08 21:01:15.533 26689] *****************************
[2020-04-08 21:01:15.538 26689] INFO: No regex whitelist entries found
[2020-04-08 21:01:15.546 26689] Compiled 0 whitelist and 5 blacklist regex filters in 9.9 msec
[2020-04-08 21:02:00.119 26689] Trying to resolve 10.0.0.1
[2020-04-08 21:02:00.120 26689] Using resolvers (added FTL as last resolver):
[2020-04-08 21:02:00.120 26689] 0: 84.200.69.80
[2020-04-08 21:02:00.120 26689] 1: 84.200.70.40
[2020-04-08 21:02:00.120 26689] 2: 127.0.0.1
[2020-04-08 21:02:00.134 26689] ---> "" (N/A)
[2020-04-08 21:02:00.167 26689] Trying to resolve 10.0.1.89
[2020-04-08 21:02:00.168 26689] Using resolvers (added FTL as last resolver):
[2020-04-08 21:02:00.168 26689] 0: 84.200.69.80
[2020-04-08 21:02:00.168 26689] 1: 84.200.70.40
[2020-04-08 21:02:00.168 26689] 2: 127.0.0.1
[2020-04-08 21:02:00.180 26689] ---> "" (N/A)
[2020-04-08 21:02:00.182 26689] Trying to resolve 10.0.0.116
[2020-04-08 21:02:00.182 26689] Using resolvers (added FTL as last resolver):
[2020-04-08 21:02:00.182 26689] 0: 84.200.69.80
[2020-04-08 21:02:00.182 26689] 1: 84.200.70.40
[2020-04-08 21:02:00.182 26689] 2: 127.0.0.1
[2020-04-08 21:02:00.194 26689] ---> "" (N/A)
[2020-04-08 21:02:00.195 26689] Trying to resolve 10.0.1.5
[2020-04-08 21:02:00.195 26689] Using resolvers (added FTL as last resolver):
[2020-04-08 21:02:00.195 26689] 0: 84.200.69.80
[2020-04-08 21:02:00.195 26689] 1: 84.200.70.40
[2020-04-08 21:02:00.195 26689] 2: 127.0.0.1
[2020-04-08 21:02:00.207 26689] ---> "" (N/A)
[2020-04-08 21:02:00.209 26689] Trying to resolve 10.0.1.64
[2020-04-08 21:02:00.209 26689] Using resolvers (added FTL as last resolver):
[2020-04-08 21:02:00.209 26689] 0: 84.200.69.80
[2020-04-08 21:02:00.209 26689] 1: 84.200.70.40
[2020-04-08 21:02:00.209 26689] 2: 127.0.0.1
[2020-04-08 21:02:00.221 26689] ---> "" (N/A)
[2020-04-08 21:02:00.222 26689] Trying to resolve 10.0.1.65
[2020-04-08 21:02:00.222 26689] Using resolvers (added FTL as last resolver):
[2020-04-08 21:02:00.222 26689] 0: 84.200.69.80
[2020-04-08 21:02:00.223 26689] 1: 84.200.70.40
[2020-04-08 21:02:00.223 26689] 2: 127.0.0.1
[2020-04-08 21:02:00.234 26689] ---> "" (N/A)
[2020-04-08 21:02:00.236 26689] Trying to resolve ::1
[2020-04-08 21:02:00.236 26689] Using resolvers (added FTL as last resolver):
[2020-04-08 21:02:00.236 26689] 0: 84.200.69.80
[2020-04-08 21:02:00.236 26689] 1: 84.200.70.40
[2020-04-08 21:02:00.236 26689] 2: 127.0.0.1
[2020-04-08 21:02:00.236 26689] ---> "localhost" (localhost)
[2020-04-08 21:02:00.236 26689] Trying to resolve 10.0.1.44
[2020-04-08 21:02:00.236 26689] Using resolvers (added FTL as last resolver):
[2020-04-08 21:02:00.236 26689] 0: 84.200.69.80
[2020-04-08 21:02:00.236 26689] 1: 84.200.70.40
[2020-04-08 21:02:00.236 26689] 2: 127.0.0.1
[2020-04-08 21:02:00.248 26689] ---> "" (N/A)
[2020-04-08 21:02:00.250 26689] Trying to resolve 10.0.1.19
[2020-04-08 21:02:00.250 26689] Using resolvers (added FTL as last resolver):
[2020-04-08 21:02:00.250 26689] 0: 84.200.69.80
[2020-04-08 21:02:00.250 26689] 1: 84.200.70.40
[2020-04-08 21:02:00.250 26689] 2: 127.0.0.1
[2020-04-08 21:02:00.262 26689] ---> "" (N/A)
[2020-04-08 21:02:00.263 26689] Trying to resolve 10.0.1.67
[2020-04-08 21:02:00.263 26689] Using resolvers (added FTL as last resolver):
[2020-04-08 21:02:00.263 26689] 0: 84.200.69.80
[2020-04-08 21:02:00.264 26689] 1: 84.200.70.40
[2020-04-08 21:02:00.264 26689] 2: 127.0.0.1
[2020-04-08 21:02:00.275 26689] ---> "" (N/A)
[2020-04-08 21:02:00.277 26689] Trying to resolve 10.0.1.12
[2020-04-08 21:02:00.277 26689] Using resolvers (added FTL as last resolver):
[2020-04-08 21:02:00.277 26689] 0: 84.200.69.80
[2020-04-08 21:02:00.277 26689] 1: 84.200.70.40
[2020-04-08 21:02:00.277 26689] 2: 127.0.0.1
[2020-04-08 21:02:00.289 26689] ---> "" (N/A)
[2020-04-08 21:02:00.290 26689] Trying to resolve 10.0.1.6
[2020-04-08 21:02:00.290 26689] Using resolvers (added FTL as last resolver):
[2020-04-08 21:02:00.291 26689] 0: 84.200.69.80
[2020-04-08 21:02:00.291 26689] 1: 84.200.70.40
[2020-04-08 21:02:00.291 26689] 2: 127.0.0.1
[2020-04-08 21:02:00.302 26689] ---> "" (N/A)
[2020-04-08 21:02:00.304 26689] Trying to resolve 10.0.0.70
[2020-04-08 21:02:00.304 26689] Using resolvers (added FTL as last resolver):
[2020-04-08 21:02:00.304 26689] 0: 84.200.69.80
[2020-04-08 21:02:00.304 26689] 1: 84.200.70.40
[2020-04-08 21:02:00.304 26689] 2: 127.0.0.1
[2020-04-08 21:02:00.316 26689] ---> "" (N/A)
[2020-04-08 21:02:00.317 26689] Trying to resolve 10.0.0.252
[2020-04-08 21:02:00.318 26689] Using resolvers (added FTL as last resolver):
[2020-04-08 21:02:00.318 26689] 0: 84.200.69.80
[2020-04-08 21:02:00.318 26689] 1: 84.200.70.40
[2020-04-08 21:02:00.318 26689] 2: 127.0.0.1
[2020-04-08 21:02:00.330 26689] ---> "" (N/A)
[2020-04-08 21:02:00.332 26689] Trying to resolve 10.0.1.3
[2020-04-08 21:02:00.332 26689] Using resolvers (added FTL as last resolver):
[2020-04-08 21:02:00.332 26689] 0: 84.200.69.80
[2020-04-08 21:02:00.332 26689] 1: 84.200.70.40
[2020-04-08 21:02:00.332 26689] 2: 127.0.0.1
[2020-04-08 21:02:00.344 26689] ---> "" (N/A)
[2020-04-08 21:02:00.346 26689] 15 / 15 client host names resolved
[2020-04-08 21:02:00.346 26689] Trying to resolve 10.0.0.254
[2020-04-08 21:02:00.346 26689] Using resolvers (added FTL as last resolver):
[2020-04-08 21:02:00.347 26689] 0: 84.200.69.80
[2020-04-08 21:02:00.347 26689] 1: 84.200.70.40
[2020-04-08 21:02:00.347 26689] 2: 127.0.0.1
[2020-04-08 21:02:00.358 26689] ---> "" (N/A)
[2020-04-08 21:02:00.360 26689] Trying to resolve 127.0.0.1
[2020-04-08 21:02:00.360 26689] Using resolvers (added FTL as last resolver):
[2020-04-08 21:02:00.360 26689] 0: 84.200.69.80
[2020-04-08 21:02:00.361 26689] 1: 84.200.70.40
[2020-04-08 21:02:00.361 26689] 2: 127.0.0.1
[2020-04-08 21:02:00.361 26689] ---> "localhost" (localhost)
[2020-04-08 21:02:00.361 26689] 2 / 2 upstream server host names resolved
[2020-04-08 21:03:00.426 26689] 0 / 15 client host names resolved
[2020-04-08 21:03:00.426 26689] 0 / 2 upstream server host names resolved