On Thu, Jun 25, 2015 at 02:13:15PM +0100, Graham Stephens wrote: > OK, it seems that when I skip-read the NSD/Unbound info I got them wrong. > Unbound sounded like a DNS cache, and NSD, unsurprisingly, a name server.
They are both name servers, but NSD is only meant to serve information authoritatively from zones it is in control of, while unbound is only meant to serve information it fetches from other (authoritative) DNS servers. > > When I looked it didn't strike me that Unbound was meant to serve the local > domain's name server needs - the config file on the Calomel site seems > awfully long just for a dozen machine names. > While local content can be served by unbound, it is not really what it was meant for. What you can do is configure "stub-zone" in unbound, pointing out a local nsd process as the target. This would then allow you to keep local zones in a master zone format like BIND does. > > That example also uses FQDNs - > I hope it will let me search for "anymachine" and not > "anymachine.myoverlylongdomainname.com" (like that old-fashioned BIND does > so well) ? ;) > Being able to search for short names is not the job of a DNS server, it is the job of your stub resolver library. -- Patrik Lundin
