Synthetic/Artificial domain support?

Guevara, Daniel Daniel_Guevara at
Tue Nov 9 01:54:39 UTC 2021


We recently switched to using Unbound instead of DNSMasq to forward DNS requests to upstream servers. As a result we were informed that the change ‘broke” AWS EMR deployments. Since AWS VPC can be large and instances come and go quickly the previous deployments leveraged doing forward and reverse DNS with a synthetic domain option:

dnsmasq --listen-address= --synth-domain=vpc.internal,,ip-

A lookup for an IP in the CIDR block will return a name that it constructs with the parameters provided (for reverse DNS), it will also work for forward look ups.

My question is if there is a similar option for Unbound? I cannot find anything in the documentation besides creating a local zone file with all the possible Ips/Names configured.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Unbound-users mailing list