Some hostnames do not resolve

Bucking_Horn · April 8, 2020, 10:56am

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.

bolausson · April 8, 2020, 11:23am

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:

Bucking_Horn · April 8, 2020, 11:48am

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

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?

bolausson · April 8, 2020, 4:01pm

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

bolausson · April 8, 2020, 7:09pm

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

gpb · April 8, 2020, 8:03pm

I have DoH setup using that guide as well, does not affect resolving host names here. Just needs the router address and domain name is my understanding.

DL6ER · April 9, 2020, 6:26am

Yeah, it's rather likely you two are affected by the same bug, I'm just wondering what is causing the failure for the two of you yet none of the other numerous beta testers?

Could you try if the situation changes with

DL6ER · April 9, 2020, 10:10am

Now this is relevant:

DL6ER · April 9, 2020, 11:46am

github.com/pi-hole/FTL

Improve internal resolver algorithm

pi-hole:release/v5.0 ← pi-hole:tweak/resolver_try_FTL_first_then_others

opened 11:45AM - 09 Apr 20 UTC

DL6ER

+136 -30

**By submitting this pull request, I confirm the following:** - [X] I have re…ad and understood the [contributors guide](https://github.com/pi-hole/pi-hole/blob/master/CONTRIBUTING.md). - [X] I have checked that [another pull request](https://github.com/pi-hole/FTL/pulls) for this purpose does not exist. - [X] I have considered, and confirmed that this submission will be valuable to others. - [X] I accept that this submission may not be used, and the pull request closed at the will of the maintainer. - [X] I give this submission freely, and claim no ownership to its content. **How familiar are you with the codebase?:** ## 10 --- This PR modifies FTL's internal resolver to work in two phases: - First, try to obtain a host name by using the internal resolver (i.e., FTL). - In a second step, only executed when FTL didn't know the answer, we ask the resolvers as configured by `resolvconf`. We've seen that the latter is necessary to get proper name resolution in docker environments. This change turns out to be necessary for some upstream servers such as 1.0.0.1 and ensures that FTL is always the first server that gets asked for host names. This PR also considers if FTL runs on a non-default (!= 53) port, e.g., in testing environments.

bolausson · April 9, 2020, 2:18pm

DEBUG_RESOLVER=true
+
pihole checkout ftl tweak/resolver_try_FTL_first_then_others
(nothing else changed as suggested in you post)

works!

All my hostnames are now resolved!

I am now just wondering, do I have to add my routers/DHCP IP as "Custom 2 (IPv4)" or not?

Cheers,
Bjoern

bolausson · April 9, 2020, 2:29pm

Just tried to remove it from “Custom 2 (IPv4)” and I can't access anything on my local network by hostname and no local clients are resolved on the dashboard so it seems to be mandatory that my router/DHCP is set in “Custom 2 (IPv4)”

gpb · April 9, 2020, 2:29pm

No, you don't need the router address here...it goes in the Settings | DNS tab.

@DL6ER Just updated and flushed my network table. Now I'm seeing "unknown" for host names for devices that do not make queries to pihole (access points, switches, etc). MAC ID / vendor data is populated, but where host name was populating it's now "unknown". FYI.

Edit (in case this helps...again this was resolving and no longer does in pihole):

pi@rpi-2:~ $ sudo dig -x 192.168.1.6 @192.168.1.1

; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> -x 192.168.1.6 @192.168.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7425
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;6.1.168.192.in-addr.arpa.      IN      PTR

;; ANSWER SECTION:
6.1.168.192.in-addr.arpa. 3600  IN      PTR     T2600G-28TS.home.

;; Query time: 0 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Apr 09 13:13:45 EDT 2020
;; MSG SIZE  rcvd: 83

bolausson · April 9, 2020, 2:33pm

Well, I tried to remove it and as said, its not working with this config on the Settings | DNS tab it works fine:

gpb · April 9, 2020, 2:43pm

Check "Use Conditional Forwarding" (bottom of page) and add your router IP and the domain name for your network (typically "local" or "home" or whatever yours is).

bolausson · April 9, 2020, 4:06pm

Indeed, this now works as well

mine is local.mydomain.de (where mydomain is just a XXXX for my real domain name)

What was the actual issue?
And what was the actual fix?

Thanks all for figuring out this issue!

Cheers,
Bjoern

DL6ER · April 9, 2020, 6:29pm

I know, there was an issue with host name resolution of clients not known to FTL. The memory issues involved were non-trivial and I figured this is not important enough to write the code for handing this (they otherwise don't get properly initialized).

gpb · April 9, 2020, 6:34pm

OK, I thought we had it working...but agreed, not critical but nice to have. Thanks!

DL6ER · April 10, 2020, 8:37am

We had, but the latest bigger issue FTL#718 and

were both caused by this. The extras work needed to initialize clients that never sent any real DNS seemed to be too much of an edge-case to be worth the effort.

The PR has been reviewed and merged. Please go back to the main branch using

pihole checkout ftl release/v5.0

bolausson · April 10, 2020, 9:05am

Switched back to release/v5.0 and everything is still working!

Pi-hole Version vDev (release/v5.0, v4.3.5-458-g2de5362)
Web Interface Version vDev (release/v5.0, v4.3.2-462-g8e51f75)
FTL Version vDev (release/v5.0, vDev-d395b3b)

Is this line in /etc/dnsmasq.d/05-rev-server.conf still mandatory after the fix?

rev-server=10.0.0.0/8,10.0.0.254

By the way, when I tried with 10.0.0.0/23 (this is my actual subnet mask) a dns restart failed.

Cheers,
Bjoern