My Unbound configuration contains an entry for domain example.com:
forward-zone:
name: "example.com"
forward-addr: 10.20.30.1
forward-addr: 10.20.30.2
It works fine for the FQDN hello.example.com resolution, but not for hello.sub.example.com (which is resolved by the same DNS server).
I can start to pile up forward-zone entries for each subzone of example.com but would prefer to use a wildcard. The documentation is silent about that - is there a way in Unbound to say "everything below example.com"?
example.com". Does the situation change if you actually add a separate entry for a subzone? Doesunbound-control list_forwardsshow any unexpected entries?forward-zonefor, say,sub.example.com, everything insub.example.comis resolved correctly. The problem is that there may be tons of various sub (and sub-sub, and sub-sub-sub, .. domains and that I do not know them. The thing I know is that they will be resolved by the DNS servers10.20.30.[1,2](that will, if needed, forward the resolution somewhere else for delegated subdomains for instance). This is why I am seriously hoping to be able to configure*.example.com(where*is greedy). And to your question: the output in the case I add subdomains is fine.hello.world.subdomain.again.example.comshould be covered by the singleexample.comentry?, whereworld.subdomain.again.example.com,subdomain.again.example.com, etc. are domains?example.comentry and its servers handle everything*.example.com- which does not work right now and I need to specifically createforward-zoneentries pointing to the same servers to handle subdomains ofexample.com). If this is how it is supposed to work, I will get some traces and post it to the mailing list.