Solved Workaround for solving DNS resolving errors

plast0000

New Member


Messages: 4

Ever faced an error like this?
Code:
ping: cannot resolve example.com: Host name lookup failure

It turns out that the problem was with unbound, I solved this problem on my laptop by disabling the validator module and removing its trust anchors.

https://www.unbound.net/documentation/howto_turnoff_dnssec.html

- open unbound.conf with a text editor
- under "server: " there's a line that contains "trust-anchor"
Delete that line then add this under "server: "
Code:
module-config: "iterator"

Save unbound.conf and reboot, it should now work normally :)
 

xtaz

Well-Known Member

Reaction score: 146
Messages: 476

Except then you don't have any DNSSEC validation. So I wouldn't exactly say that was normal.
 

kpa

Beastie's Twin

Reaction score: 1,853
Messages: 6,318

You might want to check that outgoing access to TCP port 53 is not blocked, it's common for the resolver to fall back to TCP on many of the more advanced operations when a single UDP diagram can not hold the result.
 
Top