DL6ER
April 8, 2020, 11:59am
10
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?
1 Like
DL6ER
April 8, 2020, 1:12pm
12
Thanks, please try
pihole checkout ftl tweak/more_resolver_debugging
and check again for these lines (there should be more output now).
Assuming you misesed a checkout from that command:
pi@raspberrypi:~ $ tail -n 250 /var/log/pihole-FTL.log
[2020-04-08 15:55:01.509 1363] -> Forwarded DNS queries: 39298
[2020-04-08 15:55:01.509 1363] -> Blocked DNS queries: 31748
[2020-04-08 15:55:01.509 1363] -> Unknown DNS queries: 0
[2020-04-08 15:55:01.509 1363] -> Unique domains: 4650
[2020-04-08 15:55:01.509 1363] -> Unique clients: 33
[2020-04-08 15:55:01.509 1363] -> Known forward destinations: 2
[2020-04-08 15:55:01.509 1363] Successfully accessed setupVars.conf
[2020-04-08 15:55:01.509 1363] DEBUG: argv[0] = ""
[2020-04-08 15:55:01.509 1363] DEBUG: argv[1] = "-k"
[2020-04-08 15:55:01.514 1365] PID of FTL process: 1365
[2020-04-08 15:55:01.515 1365] Listening on port 4711 for incoming IPv4 telnet connections
[2020-04-08 15:55:01.515 1365] Listening on port 4711 for incoming IPv6 telnet connections
[2020-04-08 15:55:01.515 1365] Listening on Unix socket
[2020-04-08 15:55:01.516 1365] Reloading DNS cache
[2020-04-08 15:55:01.516 1365] Blocking status is enabled
[2020-04-08 15:55:01.517 1365] *****************************
[2020-04-08 15:55:01.517 1365] * Debugging enabled *
[2020-04-08 15:55:01.517 1365] * DEBUG_DATABASE NO *
[2020-04-08 15:55:01.517 1365] * DEBUG_NETWORKING NO *
[2020-04-08 15:55:01.517 1365] * DEBUG_LOCKS NO *
[2020-04-08 15:55:01.517 1365] * DEBUG_QUERIES NO *
[2020-04-08 15:55:01.517 1365] * DEBUG_FLAGS NO *
[2020-04-08 15:55:01.517 1365] * DEBUG_SHMEM NO *
[2020-04-08 15:55:01.517 1365] * DEBUG_GC NO *
[2020-04-08 15:55:01.517 1365] * DEBUG_ARP NO *
[2020-04-08 15:55:01.517 1365] * DEBUG_REGEX NO *
[2020-04-08 15:55:01.517 1365] * DEBUG_API YES *
[2020-04-08 15:55:01.517 1365] * DEBUG_OVERTIME NO *
[2020-04-08 15:55:01.517 1365] * DEBUG_EXTBLOCKED NO *
[2020-04-08 15:55:01.517 1365] * DEBUG_CAPS NO *
[2020-04-08 15:55:01.517 1365] * DEBUG_DNSMASQ_LINES NO *
[2020-04-08 15:55:01.517 1365] * DEBUG_VECTORS NO *
[2020-04-08 15:55:01.517 1365] *****************************
[2020-04-08 15:55:01.521 1365] INFO: No regex blacklist entries found
[2020-04-08 15:55:01.548 1365] Compiled 1 whitelist and 0 blacklist regex filters in 27.9 msec
[2020-04-08 15:55:11.764 1365] Resizing "/FTL-strings" from 90112 to 94208
[2020-04-08 15:56:00.077 1365] Trying to resolve 192.168.1.154
[2020-04-08 15:56:00.078 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.078 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.078 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.078 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.104 1365] ---> "" (N/A)
[2020-04-08 15:56:00.177 1365] Trying to resolve 192.168.1.240
[2020-04-08 15:56:00.178 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.178 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.178 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.178 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.201 1365] ---> "" (N/A)
[2020-04-08 15:56:00.228 1365] Trying to resolve 192.168.1.22
[2020-04-08 15:56:00.228 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.229 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.229 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.229 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.253 1365] ---> "" (N/A)
[2020-04-08 15:56:00.255 1365] Trying to resolve 192.168.1.219
[2020-04-08 15:56:00.255 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.255 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.255 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.255 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.279 1365] ---> "" (N/A)
[2020-04-08 15:56:00.280 1365] Trying to resolve 192.168.1.133
[2020-04-08 15:56:00.280 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.280 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.281 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.281 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.304 1365] ---> "" (N/A)
[2020-04-08 15:56:00.305 1365] Trying to resolve 192.168.1.217
[2020-04-08 15:56:00.306 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.306 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.306 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.306 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.330 1365] ---> "" (N/A)
[2020-04-08 15:56:00.332 1365] Trying to resolve 192.168.1.165
[2020-04-08 15:56:00.332 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.332 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.332 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.332 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.355 1365] ---> "" (N/A)
[2020-04-08 15:56:00.357 1365] Trying to resolve 192.168.1.104
[2020-04-08 15:56:00.357 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.357 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.357 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.357 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.381 1365] ---> "" (N/A)
[2020-04-08 15:56:00.383 1365] Trying to resolve 192.168.1.14
[2020-04-08 15:56:00.383 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.383 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.383 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.383 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.406 1365] ---> "" (N/A)
[2020-04-08 15:56:00.408 1365] Trying to resolve 192.168.1.239
[2020-04-08 15:56:00.408 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.408 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.408 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.408 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.432 1365] ---> "" (N/A)
[2020-04-08 15:56:00.434 1365] Trying to resolve 192.168.1.171
[2020-04-08 15:56:00.434 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.434 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.434 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.434 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.458 1365] ---> "" (N/A)
[2020-04-08 15:56:00.460 1365] Trying to resolve 192.168.1.78
[2020-04-08 15:56:00.460 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.460 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.460 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.460 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.484 1365] ---> "" (N/A)
[2020-04-08 15:56:00.486 1365] Trying to resolve 192.168.1.105
[2020-04-08 15:56:00.486 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.486 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.486 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.486 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.511 1365] ---> "" (N/A)
[2020-04-08 15:56:00.513 1365] Trying to resolve 192.168.1.157
[2020-04-08 15:56:00.513 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.513 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.513 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.513 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.536 1365] ---> "" (N/A)
[2020-04-08 15:56:00.538 1365] Trying to resolve 192.168.1.152
[2020-04-08 15:56:00.538 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.538 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.538 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.539 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.563 1365] ---> "" (N/A)
[2020-04-08 15:56:00.565 1365] Trying to resolve 192.168.1.151
[2020-04-08 15:56:00.565 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.565 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.565 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.565 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.589 1365] ---> "" (N/A)
[2020-04-08 15:56:00.591 1365] Trying to resolve 192.168.1.143
[2020-04-08 15:56:00.591 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.591 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.591 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.591 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.615 1365] ---> "" (N/A)
[2020-04-08 15:56:00.616 1365] Trying to resolve 192.168.1.161
[2020-04-08 15:56:00.616 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.616 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.617 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.617 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.641 1365] ---> "" (N/A)
[2020-04-08 15:56:00.642 1365] Trying to resolve 192.168.1.153
[2020-04-08 15:56:00.643 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.643 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.643 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.643 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.666 1365] ---> "" (N/A)
[2020-04-08 15:56:00.668 1365] Trying to resolve 192.168.1.248
[2020-04-08 15:56:00.668 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.668 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.668 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.668 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.692 1365] ---> "" (N/A)
[2020-04-08 15:56:00.693 1365] Trying to resolve 192.168.1.18
[2020-04-08 15:56:00.694 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.694 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.694 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.694 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.718 1365] ---> "" (N/A)
[2020-04-08 15:56:00.720 1365] Trying to resolve 192.168.1.46
[2020-04-08 15:56:00.720 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.720 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.720 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.720 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.744 1365] ---> "" (N/A)
[2020-04-08 15:56:00.746 1365] Trying to resolve 192.168.1.144
[2020-04-08 15:56:00.746 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.746 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.746 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.746 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.770 1365] ---> "" (N/A)
[2020-04-08 15:56:00.771 1365] Trying to resolve 192.168.1.156
[2020-04-08 15:56:00.771 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.771 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.771 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.772 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.796 1365] ---> "" (N/A)
[2020-04-08 15:56:00.797 1365] Trying to resolve 192.168.1.238
[2020-04-08 15:56:00.797 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.797 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.797 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.798 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.821 1365] ---> "" (N/A)
[2020-04-08 15:56:00.823 1365] Trying to resolve 127.0.0.1
[2020-04-08 15:56:00.823 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.823 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.823 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.823 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.823 1365] ---> "localhost" (localhost)
[2020-04-08 15:56:00.823 1365] Trying to resolve 192.168.1.249
[2020-04-08 15:56:00.823 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.823 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.823 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.823 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.847 1365] ---> "" (N/A)
[2020-04-08 15:56:00.849 1365] Trying to resolve 192.168.1.112
[2020-04-08 15:56:00.849 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.849 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.849 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.849 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.873 1365] ---> "" (N/A)
[2020-04-08 15:56:00.875 1365] Trying to resolve 192.168.1.48
[2020-04-08 15:56:00.875 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.875 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.875 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.875 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.899 1365] ---> "" (N/A)
[2020-04-08 15:56:00.901 1365] Trying to resolve 192.168.1.86
[2020-04-08 15:56:00.901 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.901 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.901 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.901 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.926 1365] ---> "" (N/A)
[2020-04-08 15:56:00.928 1365] Trying to resolve 192.168.1.142
[2020-04-08 15:56:00.928 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.928 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.928 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.928 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.952 1365] ---> "" (N/A)
[2020-04-08 15:56:00.954 1365] Trying to resolve 192.168.1.20
[2020-04-08 15:56:00.954 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.954 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.955 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.955 1365] 2: 127.0.0.1
[2020-04-08 15:56:00.978 1365] ---> "" (N/A)
[2020-04-08 15:56:00.980 1365] Trying to resolve 192.168.1.26
[2020-04-08 15:56:00.980 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:00.980 1365] 0: 8.8.8.8
[2020-04-08 15:56:00.980 1365] 1: 0.0.0.0
[2020-04-08 15:56:00.980 1365] 2: 127.0.0.1
[2020-04-08 15:56:01.004 1365] ---> "" (N/A)
[2020-04-08 15:56:01.006 1365] 33 / 33 client host names resolved
[2020-04-08 15:56:01.007 1365] Trying to resolve 8.8.8.8
[2020-04-08 15:56:01.007 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:01.007 1365] 0: 8.8.8.8
[2020-04-08 15:56:01.007 1365] 1: 0.0.0.0
[2020-04-08 15:56:01.007 1365] 2: 127.0.0.1
[2020-04-08 15:56:01.031 1365] ---> "dns.google" (dns.google)
[2020-04-08 15:56:01.031 1365] Trying to resolve 8.8.4.4
[2020-04-08 15:56:01.032 1365] Using resolvers (added FTL as last resolver):
[2020-04-08 15:56:01.032 1365] 0: 8.8.8.8
[2020-04-08 15:56:01.032 1365] 1: 0.0.0.0
[2020-04-08 15:56:01.032 1365] 2: 127.0.0.1
[2020-04-08 15:56:01.055 1365] ---> "dns.google" (dns.google)
[2020-04-08 15:56:01.055 1365] 2 / 2 upstream server host names resolved
[2020-04-08 15:57:00.131 1365] 0 / 33 client host names resolved
[2020-04-08 15:57:00.131 1365] 0 / 2 upstream server host names resolved
pi@raspberrypi:~ $
Interestingly, it seems to work from other machines on the network
C:\Users\REDACTED>ipconfig /flushdns
Windows IP Configuration
Successfully flushed the DNS Resolver Cache.
C:\Users\REDACTED>ping osmc
Pinging osmc.lan [192.168.1.22] with 32 bytes of data:
Reply from 192.168.1.22: bytes=32 time<1ms TTL=64
Reply from 192.168.1.22: bytes=32 time<1ms TTL=64
Reply from 192.168.1.22: bytes=32 time<1ms TTL=64
Reply from 192.168.1.22: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.1.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
DL6ER
April 9, 2020, 6:24am
15
Could you try again with
FORCE_FIRST_RESOLVER=true
in /etc/pihole/pihole-FTL.conf
+ pihole restartdns
?
DL6ER
April 9, 2020, 7:45am
17
Hmm, okay, next question: Have you, by any chance, made any changes to any file inside /etc/dnsmasq.d
so FTL maybe runs on a different different port?
I guess the answer is "No", especially because
worked before as well.
Please update and test another time, I made a small mistake, causing FTL to be added as the second, instead of the first, resolver for you. Let's see if this makes any difference...
No, No changes to /etc/dnsmasq.d
That seems to have done it
pi@raspberrypi:~ $ tail -n 250 /var/log/pihole-FTL.log
[2020-04-09 09:16:00.713 9360] Using resolvers (added FTL as first resolver):
[2020-04-09 09:16:00.713 9360] 0: 127.0.0.1
[2020-04-09 09:16:00.713 9360] 1: 0.0.0.0
[2020-04-09 09:16:00.713 9360] 2: 127.0.0.1
[2020-04-09 09:16:00.738 9360] ---> "" (N/A)
[2020-04-09 09:16:00.739 9360] Trying to resolve 192.168.1.20
[2020-04-09 09:16:00.739 9360] Using resolvers (added FTL as first resolver):
[2020-04-09 09:16:00.739 9360] 0: 127.0.0.1
[2020-04-09 09:16:00.739 9360] 1: 0.0.0.0
[2020-04-09 09:16:00.739 9360] 2: 127.0.0.1
[2020-04-09 09:16:00.741 9360] ---> "ring-758b10.lan" (Ring-758b10.lan)
[2020-04-09 09:16:00.741 9360] Trying to resolve 127.0.0.1
[2020-04-09 09:16:00.741 9360] Using resolvers (added FTL as first resolver):
[2020-04-09 09:16:00.741 9360] 0: 127.0.0.1
[2020-04-09 09:16:00.741 9360] 1: 0.0.0.0
[2020-04-09 09:16:00.741 9360] 2: 127.0.0.1
[2020-04-09 09:16:00.741 9360] ---> "localhost" (localhost)
[2020-04-09 09:16:00.741 9360] Trying to resolve 192.168.1.18
[2020-04-09 09:16:00.741 9360] Using resolvers (added FTL as first resolver):
[2020-04-09 09:16:00.741 9360] 0: 127.0.0.1
[2020-04-09 09:16:00.741 9360] 1: 0.0.0.0
[2020-04-09 09:16:00.741 9360] 2: 127.0.0.1
[2020-04-09 09:16:00.744 9360] ---> "tizen.lan" (TIZEN.lan)
Now I have hostnames showing in my network page too
DL6ER
April 9, 2020, 9:55am
19
Well, this is strange, but then we know how to do it.
As there is now much more debugging output, the internal resolver got it's own setting, please remove
DEBUG_API=true
FORCE_FIRST_RESOLVER=true
and insert instead
DEBUG_RESOLVER=true
Then switch to
pihole checkout ftl tweak/resolver_try_FTL_first_then_others
and check if names appear on the dashboard (they should...).
edit Building the binaries takes some time, if you get a checkout error, please try again maybe 5 minutes later.
I still have hostnames on the web page, but that seems to have broken it according to the log file.
Its seems to now just be trying 8.8.8.8 for resolution
[2020-04-09 11:22:00.282 16905] 0: 8.8.8.8
[2020-04-09 11:22:00.283 16905] 1: 0.0.0.0
[2020-04-09 11:22:00.283 16905] 2: 0.0.0.0
[2020-04-09 11:22:00.283 16905] ---> "" (N/A)
[2020-04-09 11:22:00.285 16905] Trying to resolve 192.168.1.22
[2020-04-09 11:22:00.309 16905] No host name known to FTL, trying other servers as mandated by resolv.co nf:
DL6ER
April 9, 2020, 11:09am
21
The log output has changed, the following example belongs together:
[2020-04-09 12:30:00.457 1509] Trying to resolve 127.0.0.2
[2020-04-09 12:30:00.472 1509] No host name known to FTL, trying other servers as mandated by resolv.conf:
[2020-04-09 12:30:00.472 1509] 0: 127.0.0.53
[2020-04-09 12:30:00.472 1509] 1: 0.0.0.0
[2020-04-09 12:30:00.472 1509] 2: 0.0.0.0
[2020-04-09 12:30:00.473 1509] ---> "thinkpad-x1-carbon-3rd" (found externally)
Something found internally would look like:
[2020-04-09 12:35:00.346 2092] Trying to resolve 127.0.0.1
[2020-04-09 12:35:00.346 2092] Setting nameserver to 127.0.0.1:4711
[2020-04-09 12:35:00.347 2092] ---> "localhost" (found internally)
I pushed another small change considering that network and host byte order are not always the same so deriving and setting the port the resolver is listening on might have failed. Please try again
For reference (for those interested):
Ports and addresses are always specified in calls to the socket functions using the network byte order convention. This convention is a method of sorting bytes that is independent of specific machine architectures. Host byte order, on the other hand, sorts bytes in the manner which is most natural to the host software and hardware. There are two common host byte order methods:
Little-endian byte ordering places the least significant byte first. This method is used in Intel microprocessors, for example.
Big-endian byte ordering places the most significant byte first. This method is used in IBM® z/Architecture® and S/390® mainframes and Motorola microprocessors, for example.
The network byte order is defined to always be big-endian, which may differ from the host byte order on a particular machine. Using network byte ordering for data exchanged between hosts allows hosts using different architectures to exchange address information without confusion because of byte ordering.
Source: IBM Knowledgecenter
Same problem here:
/etc/resolv.conf
nameserver 1.0.0.1
nameserver 127.0.0.1
When manually changing /etc/resolv.conf to (reverse order of nameservers)
nameserver 127.0.0.1
nameserver 1.0.0.1
and flushing and restarting pihole the hostnames do get resolved. "arp" command now also shows local hostnames
Seems that listing 127.0.0.1 (localhost) as first nameserver in /etc/resolv.conf is critical. However after every reboot /etc/resolv.conf gets overwritten...
DL6ER
April 9, 2020, 11:28am
23
Yeah, this is a bad thing. The problem is when 1.0.0.1
responds with "does not exist" (in contrast to "I don't know"), then the second server isn't even tried. This means the server at 1.0.0.1 is incorrectly configured resp. it thinks it is the only DNS server on the planet.
Please also try
with the original resolv.conf
(how it would look like after a reboot). Even if this removes the names from arp
, FTL tries to be more clever and still get the names.
Question remains why does Pihole configures 1.0.0.1 as nameserver and does not respect my system configured DNS? Would it not be more wise or elegant if pihole leaves /etc/resolv.conf in tact in stead of overwriting?
Other question IPv6 addresses aren't resolved , is that not supported ?
DL6ER
April 9, 2020, 12:13pm
28
We don't overwrite /etc/resolv.conf
. We used to do this previously but v5.0 stops this. Whatever is in this file is written there by your system.
It is supported, for instance
dig -x ::1 @127.0.0.1 +short
ip6-localhost.
Who "knows" about the hostnames and do they get resolved with a similar dig
request?
Hi, my apologies. I judged too fast. IPv6 are resolving now ! Thanks.
When can I revert FTL to release/v5.0 branch?