search

NLnetLabs / unbound

Unbound is a validating, recursive, and caching DNS resolver.
https://nlnetlabs.nl/unbound
BSD 3-Clause "New" or "Revised" License
3k stars 346 forks source link

Cannot resolve domains for LG #1023

Open Dynamic5912 opened 6 months ago

Dynamic5912 commented 6 months ago

Hi,

I am unable to resolve any domains and sub-domains for LG.com with Unbound.

Running a RPi4 with Unbound and AdGuard Home.

AdGuard Home shows SERVFAIL as a result.

Running a dig to LG.com on the RPi results in the below:

_dig lg.com @127.0.0.1 -p 5335 ;; communications error to 127.0.0.1#5335: timed out ;; communications error to 127.0.0.1#5335: timed out ;; communications error to 127.0.0.1#5335: timed out

; <<>> DiG 9.18.24-1-Debian <<>> lg.com @127.0.0.1 -p 5335 ;; global options: +cmd ;; no servers could be reached_

Please advise if there are any other settings to check/change in the Unbound.conf file and I can test again.

Thanks.

wcawijngaards commented 6 months ago

Perhaps enable the options: verbosity: 5 and logfile: "/root/unbound.log" and log-servfail: yes. This enables lots more debug output, stores it in a file instead of spamming syslog, if you like, and the servfail log makes it log a line of text with the failure for failed lookups.

Perhaps that shows why unbound cannot look up. Also it could be possible that unbound does not receive the query at all, with the verbosity 5, it should print a line that it received the query to the log. In addition the option log-queries: yes can be used to log a line for an incoming query that arrives. The option is really meant for when all the queries need to be logged, or with log-replies also the replies, for logging purposes. But here it may reveal if the query arrives at unbound, or if there is an error further in the unbound resolver lookup process.