>Are there any plans to have rebound use dns servers provided via dhcp? >I think a nice feature would be having it read from resolv.conf. > >Wouldn't this allow us to still have the nice features rebound provides, >but get the benefits of dhcp-provided dns for roadwarriors? > >I did a quick search on misc@, and the man pages are a little light, so >sorry if this has been covered.
It has been discussed a few times, but no complete plan has formed. It is a mix of problems. If rebound is running you want libc to use rebound's data. If rebound is not running it should work as before (at least until we come up with a firm plan). rebound needs to be pointed at the right sources which requires colating the information from the various input sources (dhcp, umb(4), rtsol, etc) and then hook them up. And detect when results become wrong, and deal with a variety of startup or failure conditions. We've observed others building overly complicated solutions for this, and not been satisfied by those solutions. Something interesting happened in the last year which could play an interesting part. The introduction of pledge(2) led to cooperation between our resolver (libc/asr) and the kernel -- DNS sockets are tagged with SOCK_DNS. We could play some sort of redirection game in the kernel, and leave resolv.conf as the file that libc observes. That could be a piece of the puzzle.
