Https-dns-proxy does not resolve some domains

Sorry, I misunderstood again but the result is the same -- running nslookup with an unencrypted IP of any server (including the servers in my hdp list) returns the IP.

Just a thought, but it might be worth looking in System Log to see what it shows at the time stamp when you recreate the issue. Also compared to when you turn off H-D-P
image

You will obviously need to have DNS logging enabled:

1 Like

Call me crazy, but could it be because it has a hyphen in the domain name

Can you resolve https://www.merriam-webster.com/ ?

Just curious....

I don't know what happened but after a bunch of minor settings changes (really just enabling/disabling "additional server file" for dnsmasq, restarting HDP, and enabling/disabling the log), I can resolve that website now.
(I did see errors like "cached express-scritps.com is NODATA-IPv4" in the log before the lookup started working.)

I'll ask for help again if the issue comes back.

2 Likes

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.