This is a simple check (my longer message with debug info is waiting for moderator approval) as I have been fighting with this issue more and more often. My unbound (1.12.0 and 1.13.1) are getting unreliable more often in the sense that they cannot resolve some domains. An example domain is www.startpuntgeldzaken.nl
So, I was wondering, should unbound be able to resolve that example?
Gerben Wierda (LinkedIn)
R&A Enterprise Architecture (main site)
Book: Chess and the Art of Enterprise Architecture
Book: Mastering ArchiMate
I get absolutely no issue with unbound 1.13.1 for that domain and I have enabled about every protection unbound provides like use-caps-for-id
host www.startpuntgeldzaken.nl
www.startpuntgeldzaken.nl is an alias for nibud.truepeople.space.
nibud.truepeople.space is an alias for tp-nibud-01.truepeople.space.
tp-nibud-01.truepeople.space has address 84.22.99.176
The issue was do-tcp set to no. If this is the case, queries that require TCP fail, but they fail not with a warning that TCP has been forbidden but with an attenmpt to do TCP anyway and failing with a timeout.
G