It would ask a root nameserver for an ip address for the .com nameserver, and then ask the .com nameserver for the ip address of the example.com nameserver, then ask the example.com nameserver for further records (and may continue to recurse).
Unbound is a recursive, caching, validating name server. Personally, I run it on a container right on my Mikrotik router. I service DNS myself, and honestly it feels better. If you’re unaware of what this software can do, I do suggest looking into it a bit.
What do you mean? Where would unbound forward requests to?
It would ask a root nameserver for an ip address for the .com nameserver, and then ask the .com nameserver for the ip address of the example.com nameserver, then ask the example.com nameserver for further records (and may continue to recurse).
https://en.m.wikipedia.org/wiki/Root_name_server
Unbound is a recursive, caching, validating name server. Personally, I run it on a container right on my Mikrotik router. I service DNS myself, and honestly it feels better. If you’re unaware of what this software can do, I do suggest looking into it a bit.