Re: Two new DNS virtual packages (authoritative-name-server & recursive-name-server)
On Tue, Oct 22, 2013, at 16:29, Simon McVittie wrote:
> On 22/10/13 14:43, Ondřej Surý wrote:
> > The proposed names are:
> > authoritative-name-server - authoritative domain name server
> > recursive-name-server - recursive domain name server
> > Any objections?
> If you depend on one of these, what functionality can you rely on having
> "out of the box"? What packages do you expect to benefit from having
> these virtual packages to depend on?
Break free from the technical aspect of resolving dependencies. The
virtual package name can be useful for people wanting to install
authoritative name server, so they get a list of package that provide
> For a recursive name server, is the expected functionality "it listens
> on port 53, and will resolve DNS names without relying on any non-local,
> non-authoritative DNS servers" or something?
As far as I know this works now with bind9 and unbound.
> For an authoritative name server, all I can think of is "listens on port
> 53 and does something" - or is there some portable location where
> packages are expected to be able to put zone files, or what?
> Are simple DNS forwarders like dnsmasq, which have simplistic
> authoritative resolution for a LAN and pass the rest to an external
> recursive nameserver, expected to provide a virtual package?
I think that dnsmasq can provide recursive-name-server, even though I
think the usecases and userbases are different.
Ondřej Surý <firstname.lastname@example.org>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server