On 2012/02/13 22:35, Bjvrn Ketelaars wrote: > After some recent discussions [1, 2] on the topic of unbound in base, and > (more important) really liking the idea of an alternative for BIND in base, I > made a start with fitting the different pieces of the puzzle. What is > finished:
> 2.) Testing (read: does it compile and work) on AMD64. amd64 is easy, better questions are things like does it build/work on vax (gcc2, no shared libs), does it work on "unusual" arch like hppa, etc. > What to do with the BIND tools (dig/host/nslookup)? > > Unbound offers drill. From drill.1: "The name drill is a pun on dig. With > drill you should be able get even more information than with dig.". Proposal > therefore is to replace the BIND tools with drill. I don't think drill is quite a sufficient replacement for dig yet, and the other tools are certainly still used and I'd expect to find them in the base OS. So at this point I think they should stay. > From unbound-anchor.8 I understand that unbound-anchor can be run from the > command line, or run as part of startup scripts _before_ the actual (unbound) > DNS server is started. So there is no need for DNS. Proposal therefor is to > run unbound-anchor automatically before starting the unbound daemon (rc_pre in > unbound rc-script). This (i.e. connecting out to https://data.iana.org from the system startup scripts) should *not* happen by default even if unbound is enabled. There would need to be a separate option controlling this. > After tar/gzip the source files and Makefile wrappers weigh ~4.6MB. A bit to > large to send to this list. if anyone feels like looking at the workb&do not > hesitate to mail me. Please do. It would be nice to put them on a public server.
